Skip to content

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 23.1.1 -> 24.2.7 age adoption passing confidence

Release Notes

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

v24.2.7

Compare Source

Performance Improvements

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

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, @npmcli/agent@npm:3.0.0, @npmcli/arborist@npm:8.0.1, @npmcli/config@npm:9.0.0, @npmcli/fs@npm:4.0.0, @npmcli/git@npm:6.0.3, and 107 more.
➤ YN0085: │ - @npmcli/agent@npm:2.2.2, @npmcli/arborist@npm:7.5.1, @npmcli/config@npm:8.3.1, @npmcli/fs@npm:3.1.1, @npmcli/git@npm:5.0.7, and 106 more.
➤ YN0000: └ Completed in 3s 755ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0060: │ semantic-release is listed by your project with version 24.2.7 (pb1acc), 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: │ 112 packages were added to the project (+ 26.39 MiB).
➤ YN0000: └ Completed in 2s 467ms
➤ YN0000: ┌ Link step
➤ YN0073: │ Skipped due to mode=update-lockfile
➤ YN0000: └ Completed
➤ YN0000: · Failed with errors in 6s 368ms

@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 2 times, most recently from 7f23bf9 to e2c5630 Compare August 23, 2024 13:23
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from e2c5630 to 85afce9 Compare September 11, 2024 04:34
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 85afce9 to 5155dcc Compare September 27, 2024 19:40
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 2 times, most recently from 1606440 to 56f074f Compare October 25, 2024 19:33
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 2 times, most recently from 66d8dff to 34463f8 Compare December 4, 2024 14:53
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 34463f8 to ea76247 Compare January 3, 2025 06:27
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 2 times, most recently from 3306c25 to d21254c Compare February 15, 2025 20:34
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 2 times, most recently from b00f2e7 to 7134a2e Compare May 21, 2025 09:12
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 7134a2e to 7644ca9 Compare May 24, 2025 00:35
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 7644ca9 to 9065b1f Compare June 29, 2025 18:51
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 9065b1f to e718db9 Compare July 11, 2025 20:47
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from e718db9 to b5d930d Compare July 30, 2025 03:57
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from b5d930d to 961eb60 Compare August 13, 2025 12:14
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