feat(deps): update dependency semantic-release to v24 #17
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
d6e9b59
to
88dd336
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
88dd336
to
f5f046d
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
f5f046d
to
42d2b42
Compare
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^15.13.3->^24.0.0Release Notes
semantic-release/semantic-release (semantic-release)
v24.0.0Compare Source
Bug Fixes
BREAKING CHANGES
conventional-changelog packages. if you are installing any of these packages in addition to
semantic-release, be sure to update them as well
versions of conventional-changelog packages. if you are installing any of these packages in addition
to semantic-release, be sure to update them as well
v23.1.1Compare Source
v23.1.0Compare Source
v23.0.8Compare Source
Bug Fixes
v23.0.7Compare Source
v23.0.6Compare Source
Bug Fixes
v23.0.5Compare Source
v23.0.4Compare Source
v23.0.3Compare Source
v23.0.2Compare Source
Bug Fixes
v23.0.1Compare Source
Bug Fixes
v23.0.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
https://github.com/semantic-release/env-ci/releases/tag/v11.0.0 for more information
related to https://github.com/semantic-release/semantic-release/discussions/3088
release.config.jsas the name of your config file, it needs to be moved to a.config/directory. see https://github.com/cosmiconfig/cosmiconfig/releases/tag/v9.0.0 for more detailv22.0.12Compare Source
Bug Fixes
v22.0.11Compare Source
Bug Fixes
v22.0.10Compare Source
Bug Fixes
v22.0.9Compare Source
Bug Fixes
v22.0.8Compare Source
Bug Fixes
v22.0.7Compare Source
Bug Fixes
Features
v22.0.6Compare Source
Bug Fixes
v22.0.5Compare Source
Bug Fixes
v22.0.4Compare Source
Bug Fixes
v22.0.3Compare Source
Bug Fixes
exportsdefinition for the time being (561e2d6), closes #2968. see https://github.com/semantic-release/semantic-release/issues/2978 for more information.v22.0.2Compare Source
Bug Fixes
v22.0.1Compare Source
Bug Fixes
release-notes-generatorandcommit-analyzerplugins to stable versions (041e4f7), closes #2934v22.0.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
v20.6.1 to avoid a known node bug
v21.1.2Compare Source
Bug Fixes
v21.1.1Compare Source
Bug Fixes
v21.1.0Compare Source
Features
v21.0.9Compare Source
Bug Fixes
v21.0.8Compare Source
Bug Fixes
v21.0.7Compare Source
Bug Fixes
v21.0.6Compare Source
Bug Fixes
v21.0.5Compare Source
Bug Fixes
v21.0.4Compare Source
Bug Fixes
v21.0.3Compare Source
Bug Fixes
@semantic-release/commit-analyzertov10.0.0-beta.1(4a6b31f)@semantic-release/githubto9.0.0-beta.2(#2818) (6f19d77)v21.0.2Compare Source
Bug Fixes
v21.0.1Compare Source
Bug Fixes
v21.0.0Compare Source
BREAKING CHANGES
NPM_USERNAMEandNPM_PASSWORDis no longer supported. UseNPM_TOKENinstead.Bug Fixes
@semantic-release/npmto^10.0.0(d647433)v20.1.3Compare Source
Bug Fixes
v20.1.2Compare Source
Bug Fixes
v20.1.1Compare Source
Bug Fixes
v20.1.0Compare Source
Features
v20.0.4Compare Source
Bug Fixes
v20.0.3Compare Source
Reverts
v20.0.2Compare Source
Bug Fixes
v20.0.1Compare Source
Bug Fixes
v20.0.0Compare Source
BREAKING CHANGES
Features
Bug Fixes
v19.0.5Compare Source
Reverts
v19.0.4Compare Source
Bug Fixes
v19.0.3Compare Source
Bug Fixes
v19.0.2Compare Source
Bug Fixes
v19.0.1Compare Source
Bug Fixes
v19.0.0Compare Source
Bug Fixes
markedto resolve ReDos vulnerability (#2330) (d9e5bc0)BREAKING CHANGES
@semantic-release/npmhas also dropped support for node v15markedandmarked-terminalthat resolved the ReDoS vulnerability. removal of support of this node version should be low since it was not an LTS version and has been EOL for several months already.v18.0.1Compare Source
Bug Fixes
v18.0.0Compare Source
This is a maintenance release. An increasing amount of dependencies required a node version higher than the Node 10 version supported by
semantic-release@17. We decided to go straight to a recent Node LTS version because the release build is usually independent of others, requiring a higher node version is less disruptive to users, but helps us reduce the maintenance overhead.If you use GitHub Actions and need to bump the node version set up by
actions/node-setup, you can useoctoherd-script-bump-node-version-in-workflowsBREAKING CHANGES
node-version: the minimum required version of node is now v14.17
v17.4.7Compare Source
Bug Fixes
v17.4.6Compare Source
Bug Fixes
v17.4.5Compare Source
Bug Fixes
v17.4.4Compare Source
Bug Fixes
v17.4.3Compare Source
Bug Fixes
CVE-2021-23337(#1931) (55194c1)v17.4.2Compare Source
Bug Fixes
v17.4.1Compare Source
Bug Fixes
marked-terminal(#1829) (07f12b9)v17.4.0Compare Source
Features
v17.3.9Compare Source
Bug Fixes
v17.3.8Compare Source
Bug Fixes
v17.3.7Compare Source
Bug Fixes
v17.3.6Compare Source
Bug Fixes
v17.3.5Compare Source
Bug Fixes
v17.3.4Compare Source
Bug Fixes
v17.3.3Compare Source
Bug Fixes
v17.3.2Compare Source
Bug Fixes
v17.3.1Compare Source
Bug Fixes
v17.3.0Compare Source
Features
v17.2.4Compare Source
Bug Fixes
v17.2.3Compare Source
Bug Fixes
v17.2.2Compare Source
Bug Fixes
v17.2.1Compare Source
Reverts
v17.2.0Compare Source
Features
v17.1.2Compare Source
Bug Fixes
v17.1.1Compare Source
Bug Fixes
v17.1.0Compare Source
Features
v17.0.8Compare Source
Bug Fixes
v17.0.7Compare Source
Bug Fixes
v17.0.6Compare Source
Bug Fixes
v17.0.5Compare Source
Bug Fixes
v17.0.4Compare Source
Bug Fixes
repositoryUrlin logs (55be0ba)v17.0.3Compare Source
Bug Fixes
getGitAuthUrl(e7bede1)v17.0.2Compare Source
Bug Fixes
v17.0.1Compare Source
Bug Fixes
v17.0.0Compare Source
BREAKING CHANGES
v16.0.4Compare Source
Bug Fixes
v16.0.3Compare Source
Bug Fixes
--no-verifywhen testing the Git permissions (b54b20d)v16.0.2Compare Source
Bug Fixes
v16.0.1Compare Source
Bug Fixes
v16.0.0Compare Source
BREAKING CHANGES
v16.0.0@​betausers 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:
v{version}@​{channel}{"channels":["channel1","channel2"]}and usingnullfor the default channel (for example.{"channels":[null,"channel1","channel2"]})Require Node.js >= 10.13
Git CLI version 2.7.1 or higher is now required: The
--mergeoption of thegit tagcommand has been added in Git version 2.7.1 and is now used by semantic-releaseRegexp are not supported anymore for property matching in the
releaseRulesoption.Regex are replaced by globs. For example
/core-.*/should be changed to'core-*'.The
branchoption has been removed in favor ofbranchesThe new
branchesoption expect either an Array or a single branch definition. To migrate your configuration:master: nothing to changebranchconfiguration and want to publish only from one branch: replacebranchwithbranches("branch": "my-release-branch"=>"branches": "my-release-branch")Features
addChannelplugins to returnfalsein order to signify no release was done (e1c7269)publishplugins to returnfalsein order to signify no release was done (47484f5)Performance Improvements
git tag --merge <branch>to filter tags present in a branch history (cffe9a8)Bug Fixes
channelto publish success log (5744c5e)ERELEASEBRANCHESerror message (#1188) (37bcc9e)cioption via API and config file (2faff26)getTagHeadonly when necessary (de77a79)successplugin only once for releases added to a channel (9a023b4)addChannelfor 2 merged branches configured with the same channel (4aad9cd)Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.