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

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

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 5, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 23.1.1 -> 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

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.

@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 2 times, most recently from 45daf84 to fd75d41 Compare June 12, 2024 02:29
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 2 times, most recently from 8e4e309 to 02db0bb Compare June 20, 2024 17:45
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 02db0bb to 3564d80 Compare June 26, 2024 18:00
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 2 times, most recently from 7a3ff39 to 2aceece Compare July 10, 2024 12:01
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch 2 times, most recently from 38075ce to c46c45c Compare July 17, 2024 02:48
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from c46c45c to d51f88f Compare July 26, 2024 02:53
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from d51f88f to 93dbafa Compare August 2, 2024 17:38
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 93dbafa to c5df1f8 Compare August 18, 2024 02:56
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from c5df1f8 to 3a9faf0 Compare September 11, 2024 04:16
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 3a9faf0 to 058c7ae Compare September 27, 2024 18:15
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 058c7ae to 42dca82 Compare October 18, 2024 22:21
@renovate renovate bot force-pushed the renovate/main-semantic-release-24.x branch from 42dca82 to 47a487f Compare October 25, 2024 22:06
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