chore(deps): update dependency semantic-release to v19 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
semantic-release	^17.4.7 -> ^19.0.0

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?

• https://github.com/semantic-release/semantic-release/releases/tag/v19.0.3
• https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURI

For more information

If you have any questions or comments about this advisory:

• Open a discussion in semantic-release discussions

---

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

• bump @​semantic-release/commit-analyzer to 9.0.2 (#​2258) (7f971f3)

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

---

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]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @semantic-release/changelog@5.0.1
npm ERR! Found: semantic-release@19.0.5
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"^19.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=15.8.0 <18.0.0" from @semantic-release/changelog@5.0.1
npm ERR! node_modules/@semantic-release/changelog
npm ERR!   dev @semantic-release/changelog@"^5.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: semantic-release@17.4.7
npm ERR! node_modules/semantic-release
npm ERR!   peer semantic-release@">=15.8.0 <18.0.0" from @semantic-release/changelog@5.0.1
npm ERR!   node_modules/@semantic-release/changelog
npm ERR!     dev @semantic-release/changelog@"^5.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/590f3c/6bb444/cache/others/npm/_logs/2023-06-23T04_33_55_009Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/590f3c/6bb444/cache/others/npm/_logs/2023-06-23T04_33_55_009Z-debug-0.log

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @semantic-release/changelog@5.0.1
npm error Found: semantic-release@19.0.5
npm error node_modules/semantic-release
npm error   dev semantic-release@"^19.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer semantic-release@">=15.8.0 <18.0.0" from @semantic-release/changelog@5.0.1
npm error node_modules/@semantic-release/changelog
npm error   dev @semantic-release/changelog@"^5.0.1" from the root project
npm error
npm error Conflicting peer dependency: semantic-release@17.4.7
npm error node_modules/semantic-release
npm error   peer semantic-release@">=15.8.0 <18.0.0" from @semantic-release/changelog@5.0.1
npm error   node_modules/@semantic-release/changelog
npm error     dev @semantic-release/changelog@"^5.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-10-21T16_49_59_106Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-21T16_49_59_106Z-debug-0.log