You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What kind of vulnerability is it? Who is impacted?
Secrets that would normally be masked by semantic-release can be accidentally disclosed if they contain characters that are excluded from uri encoding by encodeURI. Occurrence is further limited to execution contexts where push access to the related repository is not available without modifying the repository url to inject credentials.
Patches
Has the problem been patched? What versions should users upgrade to?
Fixed in 19.0.3
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Secrets that do not contain characters that are excluded from encoding with encodeURI when included in a URL are already masked properly.
References
Are there any links users can visit to find out more?
deps: upgraded to the beta of the commit-analyzer plugin (dfc3d91)
deps: upgraded to the beta of the release-notes-generator plugin (4a4cd92)
BREAKING CHANGES
deps: the commit-analyzer plugin now expects to be used with the latest major 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
deps: the release-notes-generator plugin now expects to be used with the latest major
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
deps: if using release.config.js as the name of your config file, it needs to be moved to a .config/ directory or renamed to .releaserc.js to keep it in the root of the repository. see https://github.com/cosmiconfig/cosmiconfig/releases/tag/v9.0.0 for more detail
node-versions: raised the minimum node v20 requirement to v20.6 (e623cc6)
node-versions: raised the minimum required node version to v18.17 and dropped v19 support (b9f294d)
node-versions: raised the minimum supported node version w/in the v20 range to v20.6.1 (b93bef4)
BREAKING CHANGES
node-versions: the minimum supported version for the v20 range of node has been raised slightly to
v20.6.1 to avoid a known node bug
node-versions: the minimum supported node version in the v20 major range is now v20.6
node-versions: node v18.17 is now the minimum supported node version and support for v19 has been dropped
exports prevents access to internal files, but they arent intended for public use anyway
conventional-changelog-presets: the new preset format is a breaking change when compared to the previous preset format. updating to support the new format means that the old preset format is no longer supported. update your preset to the latest version to maintain compatibility. this is also important if you are using a preset outside of the list of official conventional-changelog presets since your preset will need to be updated to export async functions to match the expected preset signature.
esm: semantic-release is now ESM-only. since it is used through its own executable, the impact on consuming projects should be minimal
esm: references to plugin files in configs need to include the file extension because of executing in an ESM context
node-versions: node v18 is now the minimum required version of node. this is in line with our node support policy. please see our recommendations for releasing with a different node version than your project normally uses, if necessary.
npm-plugin: upgraded to the beta, which upgrades npm to v8 (f634b8c)
upgrade marked to resolve ReDos vulnerability (#2330) (d9e5bc0)
BREAKING CHANGES
npm-plugin:@semantic-release/npm has also dropped support for node v15
node v15 has been removed from our defined supported versions of node. this was done to upgrade to compatible versions of marked and marked-terminal that 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.
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.
renovatebot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
Mar 5, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v23 [security]
Mar 14, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
Mar 16, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v23 [security]
Mar 22, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
Mar 23, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v23 [security]
Mar 24, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
Mar 25, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v23 [security]
May 2, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
May 3, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Jun 6, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v24 [security]
Jun 28, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Jun 29, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v24 [security]
Oct 10, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Oct 11, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v24 [security]
Oct 29, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Oct 31, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v24 [security]
Dec 3, 2024
renovatebot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Dec 5, 2024
This file contains hidden or 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
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:
^17.0.4→^25.0.0GitHub Vulnerability Alerts
CVE-2022-31051
Impact
What kind of vulnerability is it? Who is impacted?
Secrets that would normally be masked by semantic-release can be accidentally disclosed if they contain characters that are excluded from uri encoding by encodeURI. Occurrence is further limited to execution contexts where push access to the related repository is not available without modifying the repository url to inject credentials.
Patches
Has the problem been patched? What versions should users upgrade to?
Fixed in 19.0.3
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Secrets that do not contain characters that are excluded from encoding with
encodeURIwhen included in a URL are already masked properly.References
Are there any links users can visit to find out more?
For more information
If you have any questions or comments about this advisory:
Release Notes
semantic-release/semantic-release (semantic-release)
v25.0.3Compare Source
Bug Fixes
v25.0.2Compare Source
Bug Fixes
v25.0.1Compare Source
Bug Fixes
v25.0.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
v24.2.9Compare Source
Bug Fixes
v24.2.8Compare Source
Bug Fixes
v24.2.7Compare Source
Performance Improvements
v24.2.6Compare Source
Bug Fixes
v24.2.5Compare Source
Bug Fixes
marked-terminal(#3742) (fb1ccd4)v24.2.4Compare Source
Bug Fixes
v24.2.3Compare Source
Bug Fixes
v24.2.2Compare Source
Bug Fixes
v24.2.1Compare Source
Bug Fixes
v24.2.0Compare Source
Features
v24.1.3Compare Source
Bug Fixes
v24.1.2Compare Source
Bug Fixes
@semantic-release/githubtov11.0.0(#3460) (43df51b)v24.1.1Compare Source
Bug Fixes
v24.1.0Compare Source
Features
warntype to globalcontext.logger(#3423) (bcc663c)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
Bug Fixes
v23.1.0Compare Source
Features
v23.0.8Compare Source
Bug Fixes
v23.0.7Compare Source
Bug Fixes
v23.0.6Compare Source
Bug Fixes
v23.0.5Compare Source
Bug Fixes
v23.0.4Compare Source
Bug Fixes
v23.0.3Compare Source
Bug Fixes
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://redirect.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 or renamed to.releaserc.jsto keep it in the root of the repository. 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 #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
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - 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.
🔕 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.