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 #128

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 11, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release ^19.0.5 -> ^24.2.0 age adoption passing confidence

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)

Configuration

📅 Schedule: 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/major-semantic-release-monorepo branch 3 times, most recently from f2dd215 to d98743c Compare May 11, 2023 14:22
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d98743c to 3bbeeb2 Compare June 2, 2023 22:04
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 48f1771 to 4d22e8c Compare June 10, 2023 01:37
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 7d43f3f to dcb2aa4 Compare July 5, 2023 04:06
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from e26b233 to 2d6dcb3 Compare August 24, 2023 20:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 2d6dcb3 to a89be1e Compare September 16, 2023 07:37
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v21 chore(deps): update dependency semantic-release to v22 Sep 16, 2023
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 6ec2533 to 9abb55d Compare September 23, 2023 00:40
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9abb55d to 8c21da6 Compare September 24, 2023 18:17
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 8ac4677 to 02d986b Compare November 3, 2023 22:37
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 02d986b to 5f676f5 Compare November 17, 2023 04:55
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from bb172f1 to b57ddd2 Compare December 12, 2023 00:42
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from b57ddd2 to ca86f72 Compare December 12, 2023 06:24
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from ca86f72 to 3798fe3 Compare January 12, 2024 22:53
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v22 chore(deps): update dependency semantic-release to v23 Jan 12, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from b9c9370 to 4b65283 Compare February 7, 2024 15:58
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 4b65283 to cea3767 Compare March 15, 2024 05:09
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from c4ab182 to ad8f9c3 Compare March 18, 2024 14:33
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from ad8f9c3 to 53ea433 Compare March 24, 2024 19:30
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from f348729 to 799b2e8 Compare April 9, 2024 23:14
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 799b2e8 to bad6ce0 Compare May 10, 2024 20:09
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from bad6ce0 to 68ca657 Compare June 1, 2024 02:14
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23 chore(deps): update dependency semantic-release to v24 Jun 1, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 68ca657 to 6a021cd Compare August 17, 2024 12:37
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6a021cd to 049b175 Compare September 11, 2024 04:38
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 049b175 to 4187280 Compare September 27, 2024 19:52
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 4187280 to 1151c96 Compare October 18, 2024 22:30
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 1151c96 to 2404bda Compare October 25, 2024 22:01
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