:arrow_up: Updates semantic-release to v19 [SECURITY]

renovate[bot] commented 1 month ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
semantic-release	`^17.4.4` -> `^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?

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`](https://togithub.com/semantic-release/semantic-release/releases/tag/v19.0.3) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v19.0.2...v19.0.3) ##### Bug Fixes - **log-repo:** use the original form of the repo url to remove the need to mask credentials ([#2459](https://togithub.com/semantic-release/semantic-release/issues/2459)) ([58a226f](https://togithub.com/semantic-release/semantic-release/commit/58a226f29c04ee56bbb02cc661f020d568849cad)), closes [#2449](https://togithub.com/semantic-release/semantic-release/issues/2449) ### [`v19.0.2`](https://togithub.com/semantic-release/semantic-release/releases/tag/v19.0.2) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v19.0.1...v19.0.2) ##### Bug Fixes - **npm-plugin:** upgraded to the stable version ([0eca144](https://togithub.com/semantic-release/semantic-release/commit/0eca144bad39bf62aa6d207766985657df4fa588)) ### [`v19.0.1`](https://togithub.com/semantic-release/semantic-release/releases/tag/v19.0.1) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v19.0.0...v19.0.1) ##### Bug Fixes - **npm-plugin:** upgraded to the latest beta version ([8097afb](https://togithub.com/semantic-release/semantic-release/commit/8097afb423cf831c72482246d977551ad1361eec)) ### [`v19.0.0`](https://togithub.com/semantic-release/semantic-release/releases/tag/v19.0.0) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v18.0.1...v19.0.0) ##### Bug Fixes - **npm-plugin:** upgraded to the beta, which upgrades npm to v8 ([f634b8c](https://togithub.com/semantic-release/semantic-release/commit/f634b8c3ca498ab170d12ebea9139d1f287ecab5)) - upgrade `marked` to resolve ReDos vulnerability ([#2330](https://togithub.com/semantic-release/semantic-release/issues/2330)) ([d9e5bc0](https://togithub.com/semantic-release/semantic-release/commit/d9e5bc06044b3493300e7bc38f80efa528e3f298)) ##### 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`](https://togithub.com/semantic-release/semantic-release/releases/tag/v18.0.1) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v18.0.0...v18.0.1) ##### Bug Fixes - bump [@semantic-release/commit-analyzer](https://togithub.com/semantic-release/commit-analyzer) to 9.0.2 ([#2258](https://togithub.com/semantic-release/semantic-release/issues/2258)) ([7f971f3](https://togithub.com/semantic-release/semantic-release/commit/7f971f3a4c7c247a936814fe7d4a080946156f73)) ### [`v18.0.0`](https://togithub.com/semantic-release/semantic-release/releases/tag/v18.0.0) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v17.4.7...v18.0.0) 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`](https://togithub.com/gr2m/octoherd-script-bump-node-version-in-workflows#readme) ##### BREAKING CHANGES **node-version:** the minimum required version of node is now v14.17 ### [`v17.4.7`](https://togithub.com/semantic-release/semantic-release/releases/tag/v17.4.7) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v17.4.6...v17.4.7) ##### Bug Fixes - **engines:** fixed defined node version to account for the higher requirement from the npm plugin ([#2088](https://togithub.com/semantic-release/semantic-release/issues/2088)) ([ea52e17](https://togithub.com/semantic-release/semantic-release/commit/ea52e1775a585ac1d7305434f90d712e3da7fd33)) ### [`v17.4.6`](https://togithub.com/semantic-release/semantic-release/releases/tag/v17.4.6) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v17.4.5...v17.4.6) ##### Bug Fixes - **marked:** reverted upgrade to v3 ([#2087](https://togithub.com/semantic-release/semantic-release/issues/2087)) ([5edff69](https://togithub.com/semantic-release/semantic-release/commit/5edff69580121deae599d070dc08ca916abb0040)) ### [`v17.4.5`](https://togithub.com/semantic-release/semantic-release/releases/tag/v17.4.5) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v17.4.4...v17.4.5) ##### Bug Fixes - **deps:** update dependency marked to v3 ([6e4beb8](https://togithub.com/semantic-release/semantic-release/commit/6e4beb8314d556524341657d88817061300259a3)) ### [`v17.4.4`](https://togithub.com/semantic-release/semantic-release/releases/tag/v17.4.4) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v17.4.3...v17.4.4) ##### Bug Fixes - corrected spelling of invalid plugin config error ([#1979](https://togithub.com/semantic-release/semantic-release/issues/1979)) ([80e1665](https://togithub.com/semantic-release/semantic-release/commit/80e1665037e8977cea7c460eae863509d6779720)) ### [`v17.4.3`](https://togithub.com/semantic-release/semantic-release/releases/tag/v17.4.3) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v17.4.2...v17.4.3) ##### Bug Fixes - bump minimal version of lodash to address `CVE-2021-23337` ([#1931](https://togithub.com/semantic-release/semantic-release/issues/1931)) ([55194c1](https://togithub.com/semantic-release/semantic-release/commit/55194c106e25c18b9671ffda5096cc8b9d35ff1a)) ### [`v17.4.2`](https://togithub.com/semantic-release/semantic-release/releases/tag/v17.4.2) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v17.4.1...v17.4.2) ##### Bug Fixes - **deps:** update dependency hosted-git-info to v4 ([#1838](https://togithub.com/semantic-release/semantic-release/issues/1838)) ([44b3344](https://togithub.com/semantic-release/semantic-release/commit/44b3344b915ee59b1eca95fd660fc4e503ac9cb8)) ### [`v17.4.1`](https://togithub.com/semantic-release/semantic-release/releases/tag/v17.4.1) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v17.4.0...v17.4.1) ##### Bug Fixes - **deps:** peer dependecy error with `marked-terminal` ([#1829](https://togithub.com/semantic-release/semantic-release/issues/1829)) ([07f12b9](https://togithub.com/semantic-release/semantic-release/commit/07f12b9df2237aafe6f696b5c47898518a8e73a0)) ### [`v17.4.0`](https://togithub.com/semantic-release/semantic-release/releases/tag/v17.4.0) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v17.3.9...v17.4.0) ##### Features - **config:** Use cosmiconfig defaults to support .cjs config files ([#1815](https://togithub.com/semantic-release/semantic-release/issues/1815)) ([3ecc196](https://togithub.com/semantic-release/semantic-release/commit/3ecc196d8ad735f6ab30b81b8f5d8b6d095e1da8)), closes [#1814](https://togithub.com/semantic-release/semantic-release/issues/1814)

Configuration

📅 Schedule: Branch creation - "" in timezone Europe/Moscow, 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.

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

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

github-actions[bot] commented 1 month ago

Thanks for opening an issue! Make sure you've followed CONTRIBUTING.md.

github-actions[bot] commented 1 month ago

Hello from PR Helper

Is your PR ready for review and processing? Mark the PR ready by including #pr-ready in a comment.

If you still have work to do, even after marking this ready. Put the PR on hold by including #pr-onhold in a comment.

github-actions[bot] commented 1 month ago

Thanks for the PR!

This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged.

socket-security[bot] commented 1 month ago

Report too large to display inline

View full report↗︎

socket-security[bot] commented 1 month ago

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Install scripts	npm/ssh2@1.15.0	Install script: install Source: `node install.js`	`npm-shrinkwrap.json`	🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

@SocketSecurity ignore npm/ssh2@1.15.0

AlexRogalskiy / screenshots