Skip to content

build(deps): update dependency semantic-release to v24 (main) #21

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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 1, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 22.0.12 -> 24.2.7 age adoption passing confidence

Release Notes

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

v24.2.7

Compare Source

v24.2.6

Compare Source

Bug Fixes

v24.2.5

Compare Source

Bug Fixes
  • deps: raise the minimum of the defined range for marked-terminal (#​3742) (fb1ccd4)

v24.2.4

Compare Source

Bug Fixes

v24.2.3

Compare Source

Bug Fixes

v24.2.2

Compare Source

Bug Fixes

v24.2.1

Compare Source

Bug Fixes

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

Bug Fixes

v24.1.0

Compare Source

Features

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

Bug Fixes

v23.1.0

Compare Source

Features

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

Bug Fixes
  • deps: update dependency find-versions to v6 (6a2b6bb)

v23.0.6

Compare Source

Bug Fixes

v23.0.5

Compare Source

Bug Fixes

v23.0.4

Compare Source

Bug Fixes

v23.0.3

Compare Source

Bug Fixes

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


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

Copy link
Contributor Author

renovate bot commented Jun 1, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock
➤ YN0000: · Yarn 4.9.2
➤ YN0000: ┌ Resolution step
➤ YN0085: │ + semantic-release@npm:24.2.7, @isaacs/fs-minipass@npm:4.0.1, @npmcli/agent@npm:3.0.0, @npmcli/arborist@npm:8.0.1, @npmcli/config@npm:9.0.0, and 157 more.
➤ YN0085: │ - @npmcli/arborist@npm:7.5.2, @npmcli/config@npm:8.3.2, @npmcli/git@npm:5.0.7, @npmcli/installed-package-contents@npm:2.1.0, and 97 more.
➤ YN0000: └ Completed in 3s 740ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0060: │ semantic-release is listed by your project with version 24.2.7 (p12250), which doesn't satisfy what @softwareventures/semantic-release-config and other dependencies request (^22.0.0 || ^23.0.0).
➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code.
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0013: │ 161 packages were added to the project (+ 31.18 MiB).
➤ YN0000: └ Completed in 3s 132ms
➤ YN0000: ┌ Link step
➤ YN0073: │ Skipped due to mode=update-lockfile
➤ YN0000: └ Completed
➤ YN0000: · Failed with errors in 7s 138ms

@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 2 times, most recently from e663080 to bf452dc Compare August 23, 2024 06:42
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from bf452dc to 6952d7e Compare September 11, 2024 06:59
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 6952d7e to a0fb316 Compare September 27, 2024 19:43
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 2 times, most recently from 70457bf to ba1c31d Compare October 25, 2024 21:11
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from ba1c31d to 81663b7 Compare January 3, 2025 07:56
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 2 times, most recently from e4b36dc to bf56634 Compare February 15, 2025 21:06
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 2 times, most recently from cae5286 to b3ba1fd Compare May 21, 2025 15:38
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from b3ba1fd to 5cc1088 Compare May 24, 2025 00:48
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 5cc1088 to 2e852b1 Compare June 29, 2025 19:02
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 2e852b1 to 08a1d05 Compare July 12, 2025 00:41
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