chore(deps): update dependency semantic-release to v17 [security] - #316
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency semantic-release to v17 [security]#316renovate[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
2 times, most recently
from
August 13, 2025 13:58
05d4252 to
e97678f
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
September 25, 2025 18:59
e97678f to
9e6590e
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
October 21, 2025 17:48
9e6590e to
2164605
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
November 11, 2025 01:00
2164605 to
3c12723
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
November 18, 2025 22:47
3c12723 to
1e1f930
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
February 2, 2026 19:27
1e1f930 to
9d09dd5
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
February 12, 2026 16:02
9d09dd5 to
a2251c4
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
March 30, 2026 21:17
a2251c4 to
a1c5238
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 8, 2026 20:00
a1c5238 to
5776078
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 29, 2026 13:49
5776078 to
4085df1
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
May 12, 2026 12:10
4085df1 to
9d9b75c
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
June 1, 2026 18:53
1ae0c32 to
c0e59af
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
June 11, 2026 11:15
c0e59af to
a7f0607
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
July 12, 2026 16:56
a7f0607 to
87837bb
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:
15.13.19→17.2.3Secret disclosure when containing characters that become URI encoded
CVE-2020-26226 / GHSA-r2j6-p67h-q639
More information
Details
Impact
Secrets that would normally be masked by
semantic-releasecan be accidentally disclosed if they contain characters that become encoded when included in a URL.Patches
Fixed in v17.2.3
Workarounds
Secrets that do not contain characters that become encoded when included in a URL are already masked properly.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
semantic-release/semantic-release (semantic-release)
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)false(751a5f1)getError(f96c660)await(9a1af4d)get-tagsalgorithm (00420a8)branchparameter frompushfunction (968b996)v15.14.0Compare Source
Features
envi-civalues to plugins context (a8c747d)v15.13.32Compare Source
Bug Fixes
v15.13.31Compare Source
Bug Fixes
v15.13.30Compare Source
Bug Fixes
v15.13.29Compare Source
Bug Fixes
v15.13.28Compare Source
Bug Fixes
v15.13.27Compare Source
Bug Fixes
v15.13.26Compare Source
Bug Fixes
v15.13.25Compare Source
Bug Fixes
v15.13.24Compare Source
Reverts
v15.13.23Compare Source
Bug Fixes
v15.13.22Compare Source
Bug Fixes
v15.13.21Compare Source
Bug Fixes
v15.13.20Compare Source
Bug Fixes
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.