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

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 4, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release ^17.0.4 -> ^19.0.3 age adoption passing confidence

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

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

v17.0.6

Compare Source

Bug Fixes

v17.0.5

Compare Source

Bug Fixes
  • adapt for semver to version 7.3.2 (0363790)

Configuration

📅 Schedule: Branch creation - "" (UTC), 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 de214ef to 118c61a Compare March 5, 2024 05:32
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23 [security] chore(deps): update dependency semantic-release to v19 [security] Mar 5, 2024
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v23 [security] Mar 14, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 7131751 to 306341d Compare March 16, 2024 11:55
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23 [security] chore(deps): update dependency semantic-release to v19 [security] Mar 16, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 306341d to 080e33d Compare March 22, 2024 23:49
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v23 [security] Mar 22, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 080e33d to 3baccf4 Compare March 23, 2024 14:58
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23 [security] chore(deps): update dependency semantic-release to v19 [security] Mar 23, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 3baccf4 to ee9eef2 Compare March 24, 2024 23:45
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v23 [security] Mar 24, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from ee9eef2 to febadd3 Compare March 25, 2024 23:49
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23 [security] chore(deps): update dependency semantic-release to v19 [security] Mar 25, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from febadd3 to 994a69b Compare April 15, 2024 05:49
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v23 [security] Apr 15, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 994a69b to a731a3b Compare April 17, 2024 05:37
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23 [security] chore(deps): update dependency semantic-release to v19 [security] Apr 17, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from a731a3b to a0a320e Compare April 21, 2024 20:55
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v23 [security] Apr 21, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from a0a320e to f01425d Compare April 22, 2024 05:32
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23 [security] chore(deps): update dependency semantic-release to v19 [security] Apr 22, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from f01425d to 4dd79fc Compare April 26, 2024 02:59
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v23 [security] Apr 26, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 4dd79fc to be406c3 Compare April 27, 2024 11:56
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23 [security] chore(deps): update dependency semantic-release to v19 [security] Apr 27, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from be406c3 to e7e0874 Compare May 2, 2024 17:42
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v23 [security] May 2, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from e7e0874 to bd36ee8 Compare May 3, 2024 02:15
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23 [security] chore(deps): update dependency semantic-release to v19 [security] May 3, 2024
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24 [security] chore(deps): update dependency semantic-release to v19 [security] Oct 11, 2024
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v24 [security] Oct 29, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 2853cd3 to 1d97627 Compare October 31, 2024 05:38
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24 [security] chore(deps): update dependency semantic-release to v19 [security] Oct 31, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 1d97627 to 733987a Compare December 3, 2024 05:59
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v24 [security] Dec 3, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 733987a to 09e8eda Compare December 5, 2024 23:48
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24 [security] chore(deps): update dependency semantic-release to v19 [security] Dec 5, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 09e8eda to 20870c3 Compare December 21, 2024 14:41
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v24 [security] Dec 21, 2024
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24 [security] chore(deps): update dependency semantic-release to v19 [security] Dec 24, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 20870c3 to 4dd3041 Compare December 24, 2024 20:30
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 4dd3041 to 196c5e8 Compare January 15, 2025 08:06
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v24 [security] Jan 15, 2025
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24 [security] chore(deps): update dependency semantic-release to v19 [security] Jan 17, 2025
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 196c5e8 to 87e65e9 Compare January 17, 2025 11:34
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v24 [security] Jan 24, 2025
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 9617324 to 11c5377 Compare January 25, 2025 03:31
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24 [security] chore(deps): update dependency semantic-release to v19 [security] Jan 25, 2025
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 11c5377 to 7bd98f1 Compare January 31, 2025 11:54
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v24 [security] Jan 31, 2025
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 7bd98f1 to 2b5cba7 Compare February 1, 2025 20:08
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24 [security] chore(deps): update dependency semantic-release to v19 [security] Feb 1, 2025
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 2b5cba7 to 9d0054e Compare February 11, 2025 07:45
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v24 [security] Feb 11, 2025
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 9d0054e to a7b1b48 Compare February 15, 2025 07:35
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24 [security] chore(deps): update dependency semantic-release to v19 [security] Feb 15, 2025
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