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 v24 #110

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

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release ^23.0.0 -> ^24.0.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/major-semantic-release-monorepo branch from 5a4070b to cbc15ef Compare July 8, 2024 03:59
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from ceb8987 to 1589d97 Compare July 29, 2024 05:08
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from c2f1c8e to 3ffca49 Compare August 19, 2024 04:37
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 4610315 to 21da337 Compare September 9, 2024 03:53
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 43bda80 to 655f20f Compare November 25, 2024 03:43
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 0431438 to d19f400 Compare December 9, 2024 04:22
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d19f400 to 7d7bccd Compare December 16, 2024 03:44
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7d7bccd to 9906b94 Compare December 23, 2024 05:15
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9906b94 to 7b53bfd Compare December 30, 2024 04:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants