Skip to content

feat(deps): update dependency semantic-release to v24 (main) #61

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # 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 23.1.1 -> 24.2.3 age adoption passing confidence

Release Notes

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

v24.2.3

Compare Source

Bug Fixes

v24.2.2

Compare Source

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

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

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.7.0
➤ YN0000: ┌ Resolution step
➤ YN0085: │ + semantic-release@npm:24.2.3, @semantic-release/commit-analyzer@npm:13.0.1, @semantic-release/github@npm:11.0.1, and 7 more.
➤ YN0085: │ - @semantic-release/commit-analyzer@npm:12.0.0, @semantic-release/github@npm:10.3.5, @semantic-release/release-notes-generator@npm:13.0.0, and 6 more.
➤ YN0000: └ Completed in 1s 288ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0060: │ semantic-release is listed by your project with version 24.2.3 (pe0ff8), 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: │ 10 packages were added to the project (+ 1.08 MiB).
➤ YN0000: └ Completed in 0s 398ms
➤ YN0000: ┌ Link step
➤ YN0073: │ Skipped due to mode=update-lockfile
➤ YN0000: └ Completed
➤ YN0000: · Failed with errors in 2s 68ms

@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 2 times, most recently from a466f03 to 1c0304d Compare June 5, 2024 14:01
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 1c0304d to 4b83c28 Compare June 11, 2024 09:37
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 4b83c28 to 7513d8d Compare July 13, 2024 15:36
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 7513d8d to 1c091fa Compare August 17, 2024 14:21
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 1c091fa to 3e4fda9 Compare September 11, 2024 07:10
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 3e4fda9 to 6b69e4f Compare September 27, 2024 19:25
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 2 times, most recently from 4b071bd to 87cbb19 Compare October 25, 2024 19:30
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 2 times, most recently from 972b357 to e493922 Compare November 26, 2024 17:21
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from e493922 to 420d4e4 Compare December 5, 2024 03:43
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 420d4e4 to 9949ec4 Compare January 7, 2025 15:36
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 4 times, most recently from 7d94323 to 072994c Compare February 15, 2025 20:29
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 072994c to 26d2a83 Compare February 22, 2025 08:53
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 26d2a83 to f8d1973 Compare March 3, 2025 08:24
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants