🚨 [security] [js] Update semantic-release 17.4.7 → 24.1.3 (major)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ semantic-release (17.4.7 → 24.1.3) · Repo

Security Advisories 🚨

🚨 Exposure of Sensitive Information to an Unauthorized Actor in semantic-release

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

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by 14 commits:

• Merge pull request #3479 from abichinger/fix/maintenance-filter
• fix(branch-naming): prevent non-range versions from being identified as maintenance branches
• chore(deps): update dependency npm-run-all2 to v6.2.4 (#3480)
• chore(deps): lock file maintenance (#3477)
• ci(action): update actions/upload-artifact action to v4.4.3 (#3474)
• chore(deps): update dependency got to v14.4.3 (#3473)
• ci(action): update actions/upload-artifact action to v4.4.2 (#3472)
• ci(action): update actions/upload-artifact action to v4.4.1 (#3469)
• ci(action): update actions/checkout action to v4.2.1 (#3468)
• chore(deps): lock file maintenance (#3467)
• chore(deps): update npm to v10.9.0 (#3464)
• chore(deps): lock file maintenance (#3461)
• docs(plugins): add semantic-release-mirror-version to plugins (#2487)
• chore(deps): lock file maintenance (#3427)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #763.

[depfu]

Closed in favor of #763.