chore(deps): update semantic-release monorepo (major)

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
@semantic-release/changelog	devDependencies	major	^3.0.2 -> ^5.0.0
@semantic-release/git	devDependencies	major	^7.0.8 -> ^9.0.0
@semantic-release/github	devDependencies	major	^5.2.10 -> ^7.0.0
@semantic-release/npm	devDependencies	major	^5.1.4 -> ^7.0.0
@semantic-release/release-notes-generator	devDependencies	major	^7.1.4 -> ^9.0.0
semantic-release	devDependencies	major	^15.13.3 -> ^17.0.0

---

Release Notes

semantic-release/changelog

v5.0.1

Compare Source

Bug Fixes

• package: update fs-extra to version 9.0.0 (997fe15)

v5.0.0

Compare Source

chore

• require Node.js >=10.18 (5ffdf49)

BREAKING CHANGES

• Require Node.js >= 10.18

v4.0.0

Compare Source

Features

• require Node.js >=10.13 (1f483af)

BREAKING CHANGES

• Require Node.js >= 10.13

semantic-release/git

v9.0.0

Compare Source

chore

• require Node.js >=10.18 (4016fcc)

BREAKING CHANGES

• Require Node.js >= 10.18

v8.0.0

Compare Source

Bug Fixes

• package: update execa to version 4.0.0 (9c1dc67)
• include deleted files in release commit (f59d20c)
• package: update aggregate-error to version 2.0.0 (3eb8f60)
• package: update execa to version 2.0.2 (9404d44)
• package: update execa to version 3.0.0 (e6af5b4)
• look for modified fiels to commit only if there files matching the globs (d97c030)
• update globby to latest version (9e2b2e5)

Features

• require Node.js >=10.13 (81955b8)
• require Node.js >=8.15 (15356b1)
• support branch parameter from semantic-release@16.0.0 (02b1f6d)

BREAKING CHANGES

• Require Node.js >= 10.13
• Require Git 2.7.1 or higher
• Require Node.js => 8.15

semantic-release/github

v7.0.5

Compare Source

Bug Fixes

• package: update fs-extra to version 9.0.0 (884dfee)

v7.0.4

Compare Source

Bug Fixes

• package: update @​octokit/rest to version 17.0.0 (e328b76)

v7.0.3

Compare Source

Bug Fixes

• package: update https-proxy-agent to version 5.0.0 (3a5d3e4)

v7.0.2

Compare Source

Bug Fixes

• address @octokit/rest deprecations (#​249) (c1ae4ac)

v7.0.1

Compare Source

Bug Fixes

• package: update globby to version 11.0.0 (e055e41)

v7.0.0

Compare Source

chore

• require Node.js >=10.18 (fb249b7)

BREAKING CHANGES

• Require Node.js >= 10.18

v6.0.2

Compare Source

Bug Fixes

• package: update http-proxy-agent to version 4.0.0 (2a0a8f8)

v6.0.1

Compare Source

Bug Fixes

• package: update issue-parser to version 6.0.0 (b02a35b)

v6.0.0

Compare Source

Bug Fixes

• adapt for latest @​octokit/rest to remove deprecation warnings (#​177) (b2bc352)
• use correct peerDependencies for semantic-release (742b521)
• use the branch.main flag to determine is the release need the prerelease flag (7aaeb0f)
• package: update @​octokit/rest to version 16.13.1 (4c756b2)
• package: update aggregate-error to version 2.0.0 (7d6b7f0)
• package: update aggregate-error to version 3.0.0 (2f08578)
• package: update p-filter to version 2.0.0 (bab986f)
• package: update p-retry to version 3.0.0 (36aab02)
• package: update p-retry to version 4.0.0 (01822de)
• also add comment/label to open issues (b69986f)
• release debug messsage in publish (0a3ed26)
• retrieve the branch name from context.branch (5f19284)
• update globby to latest version (2b5e557)
• update globby to latest version (c290940)
• when adding labels, expect labels array to be sent in request body for GHE support (a81a825)

Features

• add addChannel plugin step (589a5c4)
• append assets before release (8eb8d66)
• require Node.js >=10.13 (bd4322d)
• support nextRelease.channel property in publish step (869c827)

BREAKING CHANGES

• Require Node.js >= 10.13

semantic-release/npm

v7.0.5

Compare Source

Bug Fixes

• package: update fs-extra to version 9.0.0 (67a3109)

v7.0.4

Compare Source

Bug Fixes

• package: update tempy to version 0.5.0 (6ffff19)

v7.0.3

Compare Source

Bug Fixes

• package: update tempy to version 0.4.0 (4874bf6)

v7.0.2

Compare Source

Bug Fixes

• package: update normalize-url to version 5.0.0 (a554580)

v7.0.1

Compare Source

Bug Fixes

• package: update semver to version 7.1.2 (a58b30b)

v7.0.0

Compare Source

chore

• require Node.js >=10.18 (8140f0f)

BREAKING CHANGES

• Require Node.js >= 10.18

v6.0.0

Compare Source

Bug Fixes

• package: update execa to version 4.0.0 (d97dee5)
• package: update semver to version 6.3.0 (c515862)
• add dist-tag to publish and add-channel logs (db6ccd2)
• use correct peerDependencies for semantic-release (8b47e7b)
• package: pin npm to 6.5.0 (ddab7b7)
• package: update aggregate-error to version 2.0.0 (df53298)
• package: update aggregate-error to version 3.0.0 (3e0d5d0)
• package: update execa to version 3.0.0 (b1780c1)
• package: update npm to version 6.8.0 (2b0492e)
• package: update read-pkg to version 5.0.0 (877ce40)
• package: update vulnerable dependencies (#​185) (a96c6da)
• skip tarball move if config is cwd (a224497)
• package: update execa to version 2.0.2 (d2932ba)
• package: update registry-auth-token to version 4.0.0 (2868b2c)
• add dist-tag to publish log (2de37a1)
• Honor NPM_CONFIG_USERCONFIG setting (932ea5e)
• package: update fs-extra to version 8.0.0 (bf603e5)
• return false if the npm publish is skipped (4a41228)
• return false in addChannel if package is not published on npm (5434bab)

Features

• add addChannel plugin step (fb96126)
• require Node.js >=10.13 (6426458)
• require Node.js >=8.15 (4caf538)
• support nextRelease.channel property in publish step (b8deba7)

BREAKING CHANGES

• Require Node.js >= 10.13
• Require Node.js => 8.15

semantic-release/release-notes-generator

v9.0.1

Compare Source

Bug Fixes

• remove duplicate debug log (14129a9)

v9.0.0

Compare Source

chore

• require Node.js >=10.18 (97ab553)

BREAKING CHANGES

• Require Node.js >= 10.18

v8.0.0

Compare Source

Features

• require Node.js >=10.13 (c34dbc2)

BREAKING CHANGES

• Require Node.js >= 10.13

semantic-release/semantic-release

v17.0.7

Compare Source

Bug Fixes

• package: update marked to version 1.0.0 (#​1534) (d64db31)

v17.0.6

Compare Source

Bug Fixes

• adapt for semver to version 7.3.2 (part II) (#​1530) (431d571)

v17.0.5

Compare Source

Bug Fixes

• adapt for semver to version 7.3.2 (0363790)

v17.0.4

Compare Source

Bug Fixes

• add repositoryUrl in logs (55be0ba)

v17.0.3

Compare Source

Bug Fixes

• pass a branch name to getGitAuthUrl (e7bede1)

v17.0.2

Compare Source

Bug Fixes

• package: update marked-terminal to version 4.0.0 (8ce2d6e)

v17.0.1

Compare Source

Bug Fixes

• package: update @​semantic-release/commit-analyzer to version 8.0.0 (45695b9)
• package: update @​semantic-release/github to version 7.0.0 (c48bd3a)
• package: update @​semantic-release/npm to version 7.0.0 (f2b5826)
• package: update @​semantic-release/release-notes-generator to version 9.0.0 (3c7b114)

v17.0.0

Compare Source

BREAKING CHANGES

• Require Node.js >= 10.18

v16.0.4

Compare Source

Bug Fixes

• correct error when remote repository has no branches (c6b1076)

v16.0.3

Compare Source

Bug Fixes

• use --no-verify when testing the Git permissions (b54b20d)

v16.0.2

Compare Source

Bug Fixes

• fetch tags on repo cached by the CI (6b5b02e)

v16.0.1

Compare Source

Bug Fixes

• package: update env-ci to version 5.0.0 (3739ab5)

v16.0.0

Compare Source

BREAKING CHANGES

• ⚠️ For v16.0.0@​beta users only:

  In v16, a JSON object stored in a Git note is used to keep track of the channels on which a version has been released, the @{channel} suffix is no longer necessary.

  The tags formatted as v{version}@​{channel} will now be ignored. If you have releases using this format you will have to upgrade them:

  • Find all the versions that have been released on a branch other than the default one by searching for all tags formatted as v{version}@​{channel}
  • For each of those version:
    • Create a tag without the {@​channel} if none doesn't already exists
    • Add a Git note to the tag without the {@​channel} containing the channels on which the version was released formatted as {"channels":["channel1","channel2"]} and using null for the default channel (for example.{"channels":[null,"channel1","channel2"]})
    • Push the tags and notes
    • Update the GitHub releases that refer to a tag formatted as v{version}@​{channel} to use the tag without it
    • Delete the tags formatted as v{version}@​{channel}

• Require Node.js >= 10.13

• Git CLI version 2.7.1 or higher is now required: The --merge option of the git tag command has been added in Git version 2.7.1 and is now used by semantic-release

• Regexp are not supported anymore for property matching in the releaseRules option.

  Regex are replaced by globs. For example /core-.*/ should be changed to 'core-*'.

• The branch option has been removed in favor of branches

• The new branches option expect either an Array or a single branch definition. To migrate your configuration:

  • If you want to publish package from multiple branches, please see the configuration documentation
  • If you use the default configuration and want to publish only from master: nothing to change
  • If you use the branch configuration and want to publish only from one branch: replace branch with branches ("branch": "my-release-branch" => "branches": "my-release-branch")

Features

• allow addChannel plugins to return false in order to signify no release was done (e1c7269)
• allow publish plugins to return false in order to signify no release was done (47484f5)
• allow to release any version on a branch if up to date with next branch (916c268)
• support multiple branches and distribution channels (7b40524)
• use Git notes to store the channels on which a version has been released (b2c1b2c)
• package: update @​semantic-release/commit-analyzer to version 7.0.0 (e63e753)

Performance Improvements

• use git tag --merge <branch> to filter tags present in a branch history (cffe9a8)

Bug Fixes

• add channel to publish success log (5744c5e)
• add a flag indicate which branch is the main one (2caafba)
• Add helpful detail to ERELEASEBRANCHES error message (#​1188) (37bcc9e)
• allow multiple branches with same channel (63f51ae)
• allow to set ci option via API and config file (2faff26)
• call getTagHead only when necessary (de77a79)
• call success plugin only once for releases added to a channel (9a023b4)
• correct log when adding channel to tag (61665be)
• correctly determine next pre-release version (0457a07)
• correctly determine release to add to a channel (aec96c7)
• correctly handle skipped releases (89663d3)
• display erroring git commands properly (1edae67)
• do not call addChannelfor 2 merged branches configured with the same channel (4aad9cd)
• do not create tags in dry-run mode for released to add to a channel (97748c5)
• fetch all release branches on CI (b729183)
• fix branch type regexp to handle version with multiple digits (52ca0b3)
• fix maintenance branch regex (a022996)
• fix range regexp to handle version with multiple digits (9a04e64)
• handle branch properties set to false (751a5f1)
• harmonize parameters passed to getError (f96c660)
• ignore lasst release only if pre-release on the same channel as current branch (990e85f)
• increase next version on prerelease branch based on highest commit type (9ecc7a3)
• look also for previous prerelease versions to determine the next one (9772563)
• modify fetch function to handle CircleCI specifics (cbef9d1)
• on maintenance branch add to channel only version >= to start range (c22ae17)
• remove confusing logs when searching for releases to add to a channel (162b4b9)
• remove hack to workaround GitHub Rebase & Merge (844e0b0)
• remove unnecessary await (9a1af4d)
• simplify get-tags algorithm (00420a8)
• throws error if the commit associated with a tag cannot be found (1317348)
• update plugin versions (0785a84)
• update plugins dependencies (9890584)
• verify is branch is up to date by comparing remote and local HEAD (a8747c4)
• remove unnecessary branch parameter from push function (968b996)
• revert to the correct refspec in fetch function (9948a74)
• update plugins dependencies (73f0c77)
• repositoryUrl: on beta repositoryUrl needs auth for pre-release flows (#​1186) (3610422)

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by WhiteSource Renovate. View repository job log here.