Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 28, 2023

This PR contains the following updates:

Package Change Age Confidence
semantic-release 17.4.2 -> 19.0.3 age confidence

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
  • log-repo: use the original form of the repo url to remove the need to mask credentials (#​2459) (58a226f), closes #​2449

v19.0.2

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the stable version (0eca144)

v19.0.1

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the latest beta version (8097afb)

v19.0.0

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the beta, which upgrades npm to v8 (f634b8c)
  • upgrade marked to resolve ReDos vulnerability (#​2330) (d9e5bc0)
BREAKING CHANGES
  • npm-plugin: @semantic-release/npm has also dropped support for node v15
  • node v15 has been removed from our defined supported versions of node. this was done to upgrade to compatible versions of marked and marked-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 use octoherd-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
  • engines: fixed defined node version to account for the higher requirement from the npm plugin (#​2088) (ea52e17)

v17.4.6

Compare Source

Bug Fixes

v17.4.5

Compare Source

Bug Fixes
  • deps: update dependency marked to v3 (6e4beb8)

v17.4.4

Compare Source

Bug Fixes

v17.4.3

Compare Source

Bug Fixes
  • bump minimal version of lodash to address CVE-2021-23337 (#​1931) (55194c1)

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added automerge dependencies Pull requests that update a dependency file labels May 28, 2023
@codecov-commenter
Copy link

codecov-commenter commented May 28, 2023

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.31%. Comparing base (267be19) to head (ab4ff75).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #191   +/-   ##
=======================================
  Coverage   99.31%   99.31%           
=======================================
  Files           5        5           
  Lines         147      147           
  Branches       43       43           
=======================================
  Hits          146      146           
  Misses          1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from d21f812 to b5aab56 Compare August 13, 2025 17:45
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from b5aab56 to 3bda85d Compare August 19, 2025 15:07
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 3bda85d to 854033b Compare September 25, 2025 15:35
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 854033b to ab4ff75 Compare October 21, 2025 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant