chore(deps): update dependency semantic-release to v19 [security]#256
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency semantic-release to v19 [security]#256renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
August 29, 2022 14:11
98a0e7d to
6bca017
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 23, 2023 23:12
6bca017 to
57b0883
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 23, 2023 23:18
57b0883 to
415db5e
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 24, 2023 04:33
415db5e to
ccdbf2b
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 24, 2023 04:36
ccdbf2b to
978c3c0
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
December 15, 2023 05:01
42565dd to
931a28d
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
August 13, 2025 11:48
a0985c9 to
9bcb499
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
August 19, 2025 14:53
9bcb499 to
c1421e9
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
September 25, 2025 20:04
c1421e9 to
55803af
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
October 21, 2025 20:48
55803af to
d68f987
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
November 10, 2025 16:54
d68f987 to
f7a3571
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
November 18, 2025 19:54
f7a3571 to
0e91000
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
December 31, 2025 17:49
0e91000 to
66ace26
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
January 19, 2026 18:16
66ace26 to
c3b4020
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 5, 2026 14:02
c3b4020 to
73dc215
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
March 30, 2026 20:41
73dc215 to
001bcc5
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
April 27, 2026 23:13
001bcc5 to
95af513
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
May 12, 2026 12:15
95af513 to
3122321
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
June 1, 2026 19:40
3122321 to
d561353
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
June 11, 2026 18:56
d561353 to
b3f92ee
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
July 12, 2026 19:07
b3f92ee to
b544ae0
Compare
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
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:
17.4.7→19.0.3Exposure of Sensitive Information to an Unauthorized Actor in semantic-release
CVE-2022-31051 / GHSA-x2pg-mjhr-2m5x
More information
Details
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:
Severity
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
semantic-release/semantic-release (semantic-release)
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: (UTC)
🚦 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.