This repository was archived by the owner on Feb 28, 2023. It is now read-only.
chore(deps): update dependency semantic-release to 19.0.3 [security] #234
Conversation
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
920c499 to
0975b0f
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
0975b0f to
9b0b612
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
9b0b612 to
a8d88e1
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
a8d88e1 to
d6bdcbd
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
d6bdcbd to
6e1d409
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
293e33c to
521fc38
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
521fc38 to
a48139d
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
5 times, most recently
from
f7ea025 to
dcdb068
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
5ffd00f to
faa337d
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
8b4d38c to
aba09c1
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
33bbc8c to
366148b
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
366148b to
caeef1d
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
caeef1d to
86f974e
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
ab3d569 to
5a90a7c
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
4 times, most recently
from
15f279e to
b15b981
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
b15b981 to
e84c43d
Compare
1 task
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
4 times, most recently
from
e7f57d2 to
1cb1369
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
135b66c to
efd9f0f
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
efd9f0f to
6708f35
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
6708f35 to
67a912c
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.3GitHub 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
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:
Configuration
📅 Schedule: Branch creation - "" in timezone America/New_York, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 has been generated by Mend Renovate. View repository job log here.