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 v23 #394

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 29, 2023

Mend Renovate

This PR contains the following updates:

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

Release Notes

semantic-release/semantic-release (semantic-release)

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 - "before 4am on Monday" in timezone Europe/Lisbon, 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label May 29, 2023
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a374e4c to b3f231d Compare June 2, 2023 21:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from c3c2db6 to 0bbed23 Compare June 10, 2023 00:39
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 4d22c8e to 0fc42fe Compare July 5, 2023 03:45
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 2b566fd to 458df0e Compare August 24, 2023 17:31
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from ef32bac to 71cad40 Compare September 16, 2023 20:06
@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 ef32166 to a07052d Compare September 24, 2023 19:19
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 07a45cc to 345ed2a Compare November 3, 2023 21:16
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 345ed2a to c835020 Compare November 17, 2023 04:21
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 463df21 to ec30df8 Compare December 12, 2023 00:53
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from ec30df8 to 9309baa Compare December 12, 2023 06:25
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9309baa to 75ba8b7 Compare January 12, 2024 23:11
@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 3b71eb4 to e8241c8 Compare February 7, 2024 16:54
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from dbcefb2 to 915928b Compare March 18, 2024 15:07
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 915928b to 54be55b Compare March 24, 2024 16:16
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from d8763d9 to a365faf Compare April 9, 2024 22:15
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a365faf to 176f50e Compare May 10, 2024 18:19
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 176f50e to b78c0d8 Compare May 10, 2024 22:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants