Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Nov 28, 2020

This PR contains the following updates:

Package Change Age Confidence
semantic-release ^17.0.8 -> ^19.0.0 age 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)

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 from 9082a95 to d9ef0cf Compare December 10, 2020 02:57
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 7676960 to a33c572 Compare January 10, 2021 15:48
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 50d1499 to 2af3b52 Compare January 31, 2021 10:53
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 15 times, most recently from 8eeeff1 to f426ee8 Compare February 15, 2021 15:00
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 8 times, most recently from 97c2271 to 06ffbfe Compare February 22, 2021 06:11
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 15 times, most recently from 9718ba0 to 5780980 Compare March 6, 2021 22:51
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 5780980 to 1256e87 Compare April 26, 2021 16:15
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 1256e87 to d178204 Compare May 9, 2021 22:36
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from d178204 to 5908e38 Compare March 7, 2022 11:13
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 5908e38 to 7369488 Compare March 26, 2022 12:31
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 7369488 to 80fe82a Compare April 24, 2022 23:53
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 80fe82a to a275439 Compare May 15, 2022 19:21
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from a275439 to 529cfd0 Compare June 18, 2022 15:27
@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 18, 2022
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from ecc7a98 to f24b47b Compare August 13, 2025 13:31
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from f24b47b to e19d48c Compare August 19, 2025 11:39
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from e19d48c to 1878d71 Compare September 25, 2025 17:46
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 1878d71 to b802694 Compare October 21, 2025 19:08
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from b802694 to 385bea3 Compare November 10, 2025 22:05
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.

1 participant