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 v24 [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 -> ^24.0.0 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)

v24.2.0

Compare Source

Features
  • clarify branch existence requirement in error messages (#​3462) (05a2ea9)

v24.1.3

Compare Source

Bug Fixes
  • branch-naming: prevent non-range versions from being identified as maintenance branches (07f2672)

v24.1.2

Compare Source

Bug Fixes

v24.1.1

Compare Source

v24.1.0

Compare Source

v24.0.0

Compare Source

Bug Fixes
  • deps: upgraded to the beta of the commit-analyzer plugin (dfc3d91)
  • deps: upgraded to the beta of the release-notes-generator plugin (4a4cd92)
BREAKING CHANGES
  • deps: the commit-analyzer plugin now expects to be used with the latest major versions of
    conventional-changelog packages. if you are installing any of these packages in addition to
    semantic-release, be sure to update them as well
  • deps: the release-notes-generator plugin now expects to be used with the latest major
    versions of conventional-changelog packages. if you are installing any of these packages in addition
    to semantic-release, be sure to update them as well

v23.1.1

Compare Source

v23.1.0

Compare Source

v23.0.8

Compare Source

Bug Fixes
  • deps: rename read-pkg-up -> read-package-up (4980cba)
  • deps: rename read-pkg-up -> read-package-up (#​3249) (95a8b9e)

v23.0.7

Compare Source

v23.0.6

Compare Source

Bug Fixes

v23.0.5

Compare Source

v23.0.4

Compare Source

v23.0.3

Compare Source

v23.0.2

Compare Source

Bug Fixes

v23.0.1

Compare Source

Bug Fixes
  • deps: update dependency marked-terminal to v7 (9faded8)

v23.0.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES

related to https://github.com/semantic-release/semantic-release/discussions/3088

v22.0.12

Compare Source

Bug Fixes
  • Revert "fix(deps): update dependency cosmiconfig to v9" (#​3104) (f6f1bf1)

v22.0.11

Compare Source

Bug Fixes
  • deps: update dependency cosmiconfig to v9 (b38cd2e)

v22.0.10

Compare Source

Bug Fixes
  • revert updating cosmiconfig to v9 (88efead)

v22.0.9

Compare Source

Bug Fixes

v22.0.8

Compare Source

Bug Fixes

v22.0.7

Compare Source

Bug Fixes
Features

v22.0.6

Compare Source

Bug Fixes

v22.0.5

Compare Source

Bug Fixes

v22.0.4

Compare Source

Bug Fixes

v22.0.3

Compare Source

Bug Fixes

v22.0.2

Compare Source

Bug Fixes
  • deps: update dependency marked-terminal to v6 (8a7befe)

v22.0.1

Compare Source

Bug Fixes
  • deps: upgraded release-notes-generator and commit-analyzer plugins to stable versions (041e4f7), closes #​2934

v22.0.0

Compare Source

Bug Fixes
  • deps: updated to the latest beta of the commit analyzer plugin (03a687b)
  • deps: updated to the latest betas of the commit-analyzer and release-notes-generator plugins (de8e4e0)
  • deps: upgraded to the latest version of the npm plugin with npm v10 (a23b718)
Features
  • conventional-changelog-presets: supported new preset format (07a79ea)
  • defined exports for the package (72ab317)
  • node-versions: raised the minimum node v20 requirement to v20.6 (e623cc6)
  • node-versions: raised the minimum required node version to v18.17 and dropped v19 support (b9f294d)
  • node-versions: raised the minimum supported node version w/in the v20 range to v20.6.1 (b93bef4)
BREAKING CHANGES
  • node-versions: the minimum supported version for the v20 range of node has been raised slightly to
    v20.6.1 to avoid a known node bug
  • node-versions: the minimum supported node version in the v20 major range is now v20.6
  • node-versions: node v18.17 is now the minimum supported node version and support for v19 has been dropped
  • exports prevents access to internal files, but they arent intended for public use anyway
  • conventional-changelog-presets: the new preset format is a breaking change when compared to the previous preset format. updating to support the new format means that the old preset format is no longer supported. update your preset to the latest version to maintain compatibility. this is also important if you are using a preset outside of the list of official conventional-changelog presets since your preset will need to be updated to export async functions to match the expected preset signature.

v21.1.2

Compare Source

Bug Fixes

v21.1.1

Compare Source

Bug Fixes
  • types: included the definitions file in the published package (#​2920) (4c95c97)

v21.1.0

Compare Source

Features

v21.0.9

Compare Source

Bug Fixes

v21.0.8

Compare Source

Bug Fixes

v21.0.7

Compare Source

Bug Fixes

v21.0.6

Compare Source

Bug Fixes
  • get correct version if prerelease branch shares version with ... (#​2416) (e4229f9)

v21.0.5

Compare Source

Bug Fixes
  • deps: update dependency marked to v5 (452e1fa)

v21.0.4

Compare Source

Bug Fixes

v21.0.3

Compare Source

Bug Fixes
  • bump @semantic-release/commit-analyzer to v10.0.0-beta.1 (4a6b31f)
  • bump @semantic-release/github to 9.0.0-beta.2 (#​2818) (6f19d77)
  • deps: updated the beta plugins to stable versions (3941018)

v21.0.2

Compare Source

Bug Fixes

v21.0.1

Compare Source

Bug Fixes

v21.0.0

Compare Source

BREAKING CHANGES
  • deps: the npm plugin has updated the npm dependency to v9
  • legacy authentication using NPM_USERNAME and NPM_PASSWORD is no longer supported. Use NPM_TOKEN instead.
Bug Fixes
  • deps: bump @semantic-release/npm to ^10.0.0 (d647433)

v20.1.3

Compare Source

Bug Fixes
  • deps: update dependency execa to v7.1.1 (c38b53a)

v20.1.2

Compare Source

Bug Fixes
  • deps: update dependency cosmiconfig to v8.1.2 (fbede54)

v20.1.1

Compare Source

Bug Fixes

v20.1.0

Compare Source

Features

v20.0.4

Compare Source

Bug Fixes
  • windows: fixed issues preventing execution from windows (#​2672) (5df624c)

v20.0.3

Compare Source

Reverts

v20.0.2

Compare Source

Bug Fixes

v20.0.1

Compare Source

Bug Fixes
  • deps: update dependency cosmiconfig to v8 (f914c1e)
  • deps: update dependency hosted-git-info to v6 (c4da008)

v20.0.0

Compare Source

BREAKING CHANGES
  • esm: semantic-release is now ESM-only. since it is used through its own executable, the impact on consuming projects should be minimal
  • esm: references to plugin files in configs need to include the file extension because of executing in an ESM context
  • node-versions: node v18 is now the minimum required version of node. this is in line with our node support policy. please see our recommendations for releasing with a different node version than your project normally uses, if necessary.
Features
Bug Fixes
  • env-ci: updated to the stable esm-only version (#​2632) (918eb59)
  • secrets-masking: used the proper named import from hook-std to enable masking for stderr (#​2619) (cf6befa)

v19.0.5

Compare Source

Reverts

v19.0.4

Compare Source

Bug Fixes

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


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 v19 [security] chore(deps): update dependency semantic-release to v24 [security] Jun 28, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 25f26d4 to 78817a9 Compare June 29, 2024 08:27
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24 [security] chore(deps): update dependency semantic-release to v19 [security] Jun 29, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 78817a9 to 2be1a1b Compare July 14, 2024 23:25
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v24 [security] Jul 14, 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] Jul 15, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 2be1a1b to 4d9d317 Compare July 15, 2024 05:15
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 4d9d317 to 5afe85b Compare July 24, 2024 02:39
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to v24 [security] Jul 24, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 5afe85b to 663c475 Compare July 25, 2024 05:55
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24 [security] chore(deps): update dependency semantic-release to v19 [security] Jul 25, 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] Jul 29, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 567b1b4 to d995ce8 Compare July 30, 2024 08:29
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24 [security] chore(deps): update dependency semantic-release to v19 [security] Jul 30, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from d995ce8 to 94e084b Compare October 10, 2024 14:57
@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 10, 2024
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 94e084b to 82335ce Compare October 11, 2024 05:09
@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
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