Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 10, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release ^17.3.9 -> ^19.0.0 age adoption passing confidence

Test plan: CI should pass with updated dependencies. No review required: this is an automated dependency update PR.

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)

v17.4.2

Compare Source

Bug Fixes

v17.4.1

Compare Source

Bug Fixes

v17.4.0

Compare Source

Features

Configuration

📅 Schedule: Branch creation - "" in timezone America/Los_Angeles, 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v19 [SECURITY] Jun 27, 2022
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [SECURITY] chore(deps): update dependency semantic-release to v19 [security] Jun 28, 2022
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 175f16d to 030eb65 Compare July 1, 2022 15:51
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 030eb65 to 8eaac6f Compare August 1, 2022 21:19
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 4e8747c to d745113 Compare September 1, 2022 14:20
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v19 [security] - autoclosed Sep 22, 2022
@renovate renovate bot closed this Sep 22, 2022
@renovate renovate bot deleted the renovate/npm-semantic-release-vulnerability branch September 22, 2022 01:58
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] - autoclosed chore(deps): update dependency semantic-release to v19 [security] Sep 22, 2022
@renovate renovate bot reopened this Sep 22, 2022
@renovate renovate bot restored the renovate/npm-semantic-release-vulnerability branch September 22, 2022 04:54
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from d745113 to 7c79616 Compare October 1, 2022 10:39
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 4 times, most recently from e56248f to 5ec7d1a Compare November 3, 2022 19:02
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 3 times, most recently from e79bef8 to e01ed9a Compare December 3, 2022 17:01
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 3 times, most recently from a73ca4d to 8cbe249 Compare January 4, 2023 16:25
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v19 [security] - autoclosed Jan 24, 2023
@renovate renovate bot closed this Jan 24, 2023
@renovate renovate bot deleted the renovate/npm-semantic-release-vulnerability branch January 24, 2023 02:47
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] - autoclosed chore(deps): update dependency semantic-release to v19 [security] Jan 24, 2023
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 3 times, most recently from 6d710b7 to 66ebc8f Compare March 1, 2023 19:26
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 66a40dc to 9f01fd3 Compare April 1, 2023 17:38
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 4 times, most recently from b4632fd to abf8aac Compare May 4, 2023 19:38
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 5 times, most recently from d047c4a to e3801ef Compare June 6, 2023 03:54
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 4 times, most recently from 2531aa8 to f26d1ee Compare July 6, 2023 06:58
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 3 times, most recently from 6aecad9 to 3ec25ca Compare August 1, 2023 20:08
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from f4cc4a6 to 0c0c308 Compare September 1, 2023 15:06
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 7546873 to 94b42ef Compare October 1, 2023 15:41
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 3 times, most recently from a376864 to fdc7abe Compare November 1, 2023 19:47
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from fdc7abe to 217a7bc Compare March 1, 2024 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants