-
Notifications
You must be signed in to change notification settings - Fork 8
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(dependency maintenance): update dependency semantic-release to v19.0.3 [security] #781
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
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
June 22, 2022 08:13
025bb19
to
6cef7d6
Compare
renovate
bot
changed the title
chore(dependency maintenance): update dependency semantic-release to 19.0.3 [security]
chore(dependency maintenance): update dependency semantic-release to 19.0.3 [SECURITY]
Jun 27, 2022
renovate
bot
changed the title
chore(dependency maintenance): update dependency semantic-release to 19.0.3 [SECURITY]
chore(dependency maintenance): update dependency semantic-release to 19.0.3 [security]
Jun 28, 2022
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
3 times, most recently
from
July 4, 2022 16:05
4ae6721
to
c746aa5
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
August 17, 2022 08:34
a6d6c28
to
b66d1ac
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
September 8, 2022 08:51
2ee1da1
to
d076066
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
November 3, 2022 16:26
3587504
to
9699d16
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
November 14, 2022 15:17
9699d16
to
6976297
Compare
renovate
bot
changed the title
chore(dependency maintenance): update dependency semantic-release to 19.0.3 [security]
chore(dependency maintenance): update dependency semantic-release to v19.0.3 [security]
Mar 23, 2023
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
3 times, most recently
from
February 26, 2024 10:53
f1eb354
to
5428602
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
March 28, 2024 06:26
882db91
to
f6970fd
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
10 times, most recently
from
April 10, 2024 09:33
c2d556c
to
5452467
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
6 times, most recently
from
June 4, 2024 11:57
c3ca948
to
b14b174
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
4 times, most recently
from
June 26, 2024 12:43
43fed10
to
7e3d84a
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
3 times, most recently
from
July 10, 2024 13:05
860df19
to
329c390
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
8 times, most recently
from
August 6, 2024 13:21
a896c5a
to
84edf3b
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
4 times, most recently
from
August 23, 2024 10:02
1df6d40
to
541a2c1
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
September 16, 2024 10:07
b70fd4f
to
37f7fb5
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
September 25, 2024 15:32
37f7fb5
to
b7002d2
Compare
…v19.0.3 [security]
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
September 25, 2024 15:39
b7002d2
to
e108a36
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
19.0.2
->19.0.3
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
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.