chore(deps): update dependency semantic-release to v19 [security] - #93
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency semantic-release to v19 [security]#93renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
August 13, 2025 11:29
4446b5f to
5f95319
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
August 19, 2025 19:02
5f95319 to
883f5e7
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
September 25, 2025 19:06
883f5e7 to
6042bfa
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
October 21, 2025 23:56
6042bfa to
82c2b9b
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
November 10, 2025 17:45
82c2b9b to
dd7bac4
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
December 31, 2025 12:34
dd7bac4 to
629a670
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
January 19, 2026 20:03
629a670 to
61fbc25
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
February 2, 2026 15:28
61fbc25 to
7cb3176
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
February 12, 2026 11:04
7cb3176 to
558a813
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
March 5, 2026 17:26
558a813 to
729c2a8
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
April 1, 2026 17:33
729c2a8 to
b087540
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
April 8, 2026 19:40
b087540 to
93d1d97
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
April 29, 2026 13:01
93d1d97 to
fdbcd3f
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
May 12, 2026 15:45
fdbcd3f to
f88aa33
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
June 1, 2026 16:46
f6b104c to
c0bc6a8
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
June 11, 2026 14:48
c0bc6a8 to
2a0e186
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
July 12, 2026 10:39
2a0e186 to
9c1d4f5
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
July 30, 2026 16:44
128f3af to
94921c0
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
August 11, 2026 21:36
94921c0 to
f871cab
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
August 26, 2026 20:38
f871cab to
1ab3577
Compare
renovate
Bot
force-pushed
the
dev-dependency-renovate/npm-semantic-release-vulnerability
branch
from
September 2, 2026 19:48
1ab3577 to
bffc49b
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.2→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
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)Configuration
📅 Schedule: (UTC)
🚦 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.