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] #273

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 23, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release ^17.0.6 -> ^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-2020-26226

Impact

Secrets that would normally be masked by semantic-release can be accidentally disclosed if they contain characters that become encoded when included in a URL.

Patches

Fixed in v17.2.3

Workarounds

Secrets that do not contain characters that become encoded when included in a URL are already masked properly.

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

v17.3.9

Compare Source

Bug Fixes

v17.3.8

Compare Source

Bug Fixes
  • deps: update dependency marked to v2 (a2eaed0)

v17.3.7

Compare Source

Bug Fixes

v17.3.6

Compare Source

Bug Fixes

v17.3.5

Compare Source

Bug Fixes

v17.3.4

Compare Source

Bug Fixes

v17.3.3

Compare Source

Bug Fixes

v17.3.2

Compare Source

Bug Fixes

v17.3.1

Compare Source

Bug Fixes

v17.3.0

Compare Source

Features

v17.2.4

Compare Source

Bug Fixes

v17.2.3

Compare Source

Bug Fixes
  • mask secrets when characters get uri encoded (ca90b34)

v17.2.2

Compare Source

Bug Fixes
  • don't parse port as part of the path in repository URLs (#​1671) (77a75f0)
  • use valid git credentials when multiple are provided (#​1669) (2bf3771)

v17.2.1

Compare Source

Reverts

v17.2.0

Compare Source

Features
  • throw an Error if package.json has duplicate "repository" key (#​1656) (b8fb35c)

v17.1.2

Compare Source

Bug Fixes

v17.1.1

Compare Source

Bug Fixes

v17.1.0

Compare Source

Features
  • bitbucket-basic-auth: support for bitbucket server basic auth (#​1578) (a465801)

v17.0.8

Compare Source

Bug Fixes
  • prevent false positive secret replacement for Golang projects (#​1562) (eed1d3c)

v17.0.7

Compare Source

Bug Fixes

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 8 times, most recently from 362ea49 to 8d0f785 Compare March 30, 2022 16:14
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 7 times, most recently from 50b59db to b53a816 Compare April 6, 2022 17:43
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 9 times, most recently from aef07f9 to 075d7eb Compare April 14, 2022 19:48
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 4 times, most recently from 639f395 to cfea432 Compare April 20, 2022 03:23
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 7 times, most recently from 33a49f8 to 13c28f7 Compare May 5, 2022 04:11
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 13c28f7 to 17a023b Compare June 10, 2022 04:52
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v17.2.3 [security] chore(deps): update dependency semantic-release to v19 [security] Jun 10, 2022
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 17a023b to 50e5dbd Compare June 19, 2022 03:27
@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 from 50e5dbd to d60d3de Compare July 1, 2022 15:54
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from d60d3de to 0ad27a0 Compare August 5, 2022 01:27
@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 Aug 22, 2022
@renovate renovate bot closed this Aug 22, 2022
@renovate renovate bot deleted the renovate/npm-semantic-release-vulnerability branch August 22, 2022 21:10
@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] Aug 23, 2022
@renovate renovate bot reopened this Aug 23, 2022
@renovate renovate bot restored the renovate/npm-semantic-release-vulnerability branch August 23, 2022 00:15
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 0ad27a0 to 35b31f0 Compare September 1, 2022 13:17
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] Update dependency semantic-release to v19 [SECURITY] Dec 17, 2022
@renovate renovate bot changed the title Update dependency semantic-release to v19 [SECURITY] chore(deps): update dependency semantic-release to v19 [security] Dec 17, 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] - autoclosed Jan 19, 2023
@renovate renovate bot closed this Jan 19, 2023
@renovate renovate bot deleted the renovate/npm-semantic-release-vulnerability branch January 19, 2023 04:40
@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 19, 2023
@renovate renovate bot reopened this Jan 19, 2023
@renovate renovate bot restored the renovate/npm-semantic-release-vulnerability branch January 19, 2023 08:07
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.

0 participants