Closed renovate[bot] closed 7 months ago
Hey! Changelogs info seems to be missing or might be in incorrect format. Please use the below template in PR description to ensure Changelogg can detect your changes:
- (tag) changelog_text
or
```
- tag: changelog_text
```
**OR**
You can add tag in PR header or while doing a commit too
```
(tag) PR header
```
or
```
tag: PR header
```
Valid tags: **added** / **feat**, **changed**, **deprecated**, **fixed** / **fix**, **removed**, **security**, **build**, **ci**, **chore**, **docs**, **perf**, **refactor**, **revert**, **style**, **test**
Thanks!
For more info, check out [changelogg docs](https://docs.changelogg.io/)
Pull request by bot. No need to analyze
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.
Thanks for opening an issue! Make sure you've followed CONTRIBUTING.md.
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.
This PR contains the following updates:
^18.0.1
->^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:
Release Notes
semantic-release/semantic-release
### [`v19.0.5`](https://togithub.com/semantic-release/semantic-release/releases/tag/v19.0.5) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v19.0.4...v19.0.5) ##### Reverts - Revert "fix(deps): update dependency yargs to v17" ([#2534](https://togithub.com/semantic-release/semantic-release/issues/2534)) ([8f07522](https://togithub.com/semantic-release/semantic-release/commit/8f075227eb10f08c9dda41c4930b6c1fb8ee779f)), closes [#2534](https://togithub.com/semantic-release/semantic-release/issues/2534) [#2533](https://togithub.com/semantic-release/semantic-release/issues/2533) ### [`v19.0.4`](https://togithub.com/semantic-release/semantic-release/releases/tag/v19.0.4) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v19.0.3...v19.0.4) ##### Bug Fixes - **deps:** update dependency yargs to v17 ([#1912](https://togithub.com/semantic-release/semantic-release/issues/1912)) ([f419080](https://togithub.com/semantic-release/semantic-release/commit/f419080fbf86c6319b08ee6b5299525ecc8ee831)) ### [`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.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.
This PR has been generated by Mend Renovate. View repository job log here.