-
Notifications
You must be signed in to change notification settings - Fork 0
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] #93
base: main
Are you sure you want to change the base?
Conversation
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
📊 Package size report No changes
Unchanged files
🤖 This report was automatically generated by pkg-size-action |
1ea94a9
to
536e803
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
536e803
to
9e42163
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
ad0ca4a
to
22c9a2a
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
22c9a2a
to
2b53ebf
Compare
Quality Gate passedIssues Measures |
1e72d51
to
2b53ebf
Compare
Quality Gate passedIssues Measures |
This PR contains the following updates:
18.0.1
->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
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.Configuration
📅 Schedule: Branch creation - "" (UTC), 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.