-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update dependency semantic-release to v19 [security] #189
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/npm-semantic-release-vulnerability
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v19 [SECURITY]
Jun 27, 2022
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [SECURITY]
chore(deps): update dependency semantic-release to v19 [security]
Jun 28, 2022
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
July 1, 2022 15:51
175f16d
to
030eb65
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
August 1, 2022 21:19
030eb65
to
8eaac6f
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
September 1, 2022 14:20
4e8747c
to
d745113
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v19 [security] - autoclosed
Sep 22, 2022
renovate
bot
deleted the
renovate/npm-semantic-release-vulnerability
branch
September 22, 2022 01:58
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security] - autoclosed
chore(deps): update dependency semantic-release to v19 [security]
Sep 22, 2022
renovate
bot
restored the
renovate/npm-semantic-release-vulnerability
branch
September 22, 2022 04:54
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
October 1, 2022 10:39
d745113
to
7c79616
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
4 times, most recently
from
November 3, 2022 19:02
e56248f
to
5ec7d1a
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
3 times, most recently
from
December 3, 2022 17:01
e79bef8
to
e01ed9a
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
3 times, most recently
from
January 4, 2023 16:25
a73ca4d
to
8cbe249
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v19 [security] - autoclosed
Jan 24, 2023
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security] - autoclosed
chore(deps): update dependency semantic-release to v19 [security]
Jan 24, 2023
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
March 1, 2023 19:26
6d710b7
to
66ebc8f
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
April 1, 2023 17:38
66a40dc
to
9f01fd3
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
4 times, most recently
from
May 4, 2023 19:38
b4632fd
to
abf8aac
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
5 times, most recently
from
June 6, 2023 03:54
d047c4a
to
e3801ef
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
4 times, most recently
from
July 6, 2023 06:58
2531aa8
to
f26d1ee
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
3 times, most recently
from
August 1, 2023 20:08
6aecad9
to
3ec25ca
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
September 1, 2023 15:06
f4cc4a6
to
0c0c308
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
October 1, 2023 15:41
7546873
to
94b42ef
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
3 times, most recently
from
November 1, 2023 19:47
a376864
to
fdc7abe
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 1, 2024 13:34
fdc7abe
to
217a7bc
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
October 1, 2024 13:51
217a7bc
to
f3481b2
Compare
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.3.9
->^19.0.0
Test plan: CI should pass with updated dependencies. No review required: this is an automated dependency update PR.
GitHub 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
encodeURI
when 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)
v19.0.3
Compare Source
Bug Fixes
v19.0.2
Compare Source
Bug Fixes
v19.0.1
Compare Source
Bug Fixes
v19.0.0
Compare Source
Bug Fixes
marked
to resolve ReDos vulnerability (#2330) (d9e5bc0)BREAKING CHANGES
@semantic-release/npm
has also dropped support for node v15marked
andmarked-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.v18.0.1
Compare Source
Bug Fixes
v18.0.0
Compare 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-workflows
BREAKING CHANGES
node-version: the minimum required version of node is now v14.17
v17.4.7
Compare Source
Bug Fixes
v17.4.6
Compare Source
Bug Fixes
v17.4.5
Compare Source
Bug Fixes
v17.4.4
Compare Source
Bug Fixes
v17.4.3
Compare Source
Bug Fixes
CVE-2021-23337
(#1931) (55194c1)v17.4.2
Compare Source
Bug Fixes
v17.4.1
Compare Source
Bug Fixes
marked-terminal
(#1829) (07f12b9)v17.4.0
Compare Source
Features
Configuration
📅 Schedule: Branch creation - "" in timezone America/Los_Angeles, 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.