Skip to content

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

Open
renovate[bot] wants to merge 1 commit into
betafrom
renovate/npm-semantic-release-vulnerability
Open

chore(deps): update dependency semantic-release to v19 [security]#143
renovate[bot] wants to merge 1 commit into
betafrom
renovate/npm-semantic-release-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Jun 18, 2022

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
semantic-release 17.2.319.0.3 age confidence

Exposure of Sensitive Information to an Unauthorized Actor in semantic-release

CVE-2022-31051 / GHSA-x2pg-mjhr-2m5x

More information

Details

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:

Severity

  • CVSS Score: 4.4 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


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

Configuration

📅 Schedule: (in timezone America/Sao_Paulo)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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.

@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 8e79d4c to 529b431 Compare August 13, 2025 16:49
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 529b431 to bef913d Compare August 19, 2025 17:13
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from bef913d to 988465e Compare September 25, 2025 21:23
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 988465e to 278aa56 Compare October 21, 2025 13:59
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 278aa56 to 5f0e655 Compare November 10, 2025 20:39
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 5f0e655 to ec94924 Compare December 31, 2025 12:39
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from ec94924 to 55f8018 Compare January 19, 2026 17:40
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 55f8018 to a3f9982 Compare February 2, 2026 21:45
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from a3f9982 to e18ba4c Compare February 12, 2026 15:46
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from e18ba4c to b2f18ba Compare March 5, 2026 18:06
@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 Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/npm-semantic-release-vulnerability branch March 27, 2026 00:52
@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] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from b2f18ba to b51e34d Compare March 30, 2026 20:46
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from b51e34d to 64bdec7 Compare April 8, 2026 21:13
@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 Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@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] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 3 times, most recently from 5f60c07 to d6e120e Compare April 29, 2026 10:06
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from d6e120e to 38938b4 Compare May 12, 2026 11:32
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 38938b4 to 6ad5be4 Compare May 28, 2026 20:57
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 6ad5be4 to 0e604db Compare June 11, 2026 14:41
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 0e604db to 28a0ec2 Compare July 12, 2026 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants