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.0.3 [security] #427
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 }}
Could not load tags
Nothing to show
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 19, 2022 04:11
bffb11c
to
b1eaa9f
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
June 26, 2022 04:13
b1eaa9f
to
0c7c33e
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19.0.3 [security]
chore(deps): update dependency semantic-release to v19.0.3 [SECURITY]
Jun 27, 2022
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19.0.3 [SECURITY]
chore(deps): update dependency semantic-release to v19.0.3 [security]
Jun 28, 2022
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
July 9, 2022 00:52
2c142e2
to
2ddd8cf
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
July 23, 2022 01:12
2ddd8cf
to
bf9928b
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
August 7, 2022 04:10
bf9928b
to
f844d69
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
August 20, 2022 02:01
f844d69
to
a6c504a
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
August 28, 2022 12:18
6bdb1e8
to
f5a3449
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
September 24, 2022 03:12
f5a3449
to
927dacb
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
October 9, 2022 05:04
927dacb
to
bc1082a
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
October 23, 2022 04:15
bc1082a
to
b786d5e
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
November 12, 2022 03:36
b786d5e
to
7f10a66
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
November 20, 2022 05:07
7f10a66
to
9222f88
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
December 4, 2022 06:16
9222f88
to
621a7cb
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19.0.3 [security]
chore(deps): update dependency semantic-release to v19.0.3 [security] - autoclosed
Dec 14, 2022
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19.0.3 [security] - autoclosed
chore(deps): update dependency semantic-release to v19.0.3 [security]
Dec 14, 2022
renovate
bot
restored the
renovate/npm-semantic-release-vulnerability
branch
December 14, 2022 06:10
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
December 18, 2022 06:39
621a7cb
to
dbf6d01
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19.0.3 [security]
chore(deps): update dependency semantic-release to v19.0.3 [security] - autoclosed
Dec 30, 2022
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19.0.3 [security] - autoclosed
chore(deps): update dependency semantic-release to v19.0.3 [security]
Dec 30, 2022
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19.0.3 [security]
chore(deps): update dependency semantic-release to v19.0.3 [security] - autoclosed
Jan 29, 2023
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19.0.3 [security] - autoclosed
chore(deps): update dependency semantic-release to v19.0.3 [security]
Jan 29, 2023
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
February 4, 2023 02:17
060d4b8
to
a50dc74
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
February 12, 2023 08:42
a50dc74
to
2fd62e4
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19.0.3 [security]
chore(deps): update dependency semantic-release to v19.0.3 [security] - autoclosed
Mar 3, 2023
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19.0.3 [security] - autoclosed
chore(deps): update dependency semantic-release to v19.0.3 [security]
Mar 3, 2023
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 4, 2023 08:20
2fd62e4
to
26c186b
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
March 12, 2023 05:04
0c14b2e
to
0f4f9fa
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19.0.3 [security]
chore(deps): update dependency semantic-release to v19.0.3 [security] - autoclosed
Apr 27, 2023
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19.0.3 [security] - autoclosed
chore(deps): update dependency semantic-release to v19.0.3 [security]
Apr 27, 2023
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 27, 2023 05:20
0f4f9fa
to
f5d9242
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
July 29, 2023 00:03
37d5a73
to
502e4a2
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
April 20, 2024 01:37
444c1ee
to
35ebb5c
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 21, 2024 06:10
35ebb5c
to
6958680
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 - "" in timezone Europe/Zagreb, Automerge - At any time (no schedule defined).
🚦 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 has been generated by Mend Renovate. View repository job log here.