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 #222

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 30, 2024

This PR contains the following updates:

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

Release Notes

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

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

v23.1.1

Compare Source

v23.1.0

Compare Source

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

v23.0.6

Compare Source

Bug Fixes

v23.0.5

Compare Source

v23.0.4

Compare Source

v23.0.3

Compare Source

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 - "before 5am every weekday" in timezone America/New_York, Automerge - "every weekday" in timezone America/New_York.

🚦 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 requested a review from kongponents-bot as a code owner January 30, 2024 09:54
@renovate renovate bot requested a review from adamdehaven as a code owner January 30, 2024 09:54
@renovate renovate bot requested review from jillztom and a team as code owners January 30, 2024 09:54
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9045289 to 139cd03 Compare February 12, 2024 09:18
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 139cd03 to 29e706a Compare February 21, 2024 06:13
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 29e706a to c2b068a Compare February 22, 2024 07:21
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from c2b068a to edd0f0f Compare February 27, 2024 07:11
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from edd0f0f to 9696117 Compare March 4, 2024 06:25
kongponents-bot
kongponents-bot previously approved these changes Mar 4, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9696117 to 61f7026 Compare March 5, 2024 06:38
kongponents-bot
kongponents-bot previously approved these changes Mar 5, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 61f7026 to 96e3094 Compare March 13, 2024 04:25
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 96e3094 to decb786 Compare March 25, 2024 07:23
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5e0dabc to f4ea149 Compare July 2, 2024 05:19
kongponents-bot
kongponents-bot previously approved these changes Jul 2, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f4ea149 to 6316db4 Compare July 15, 2024 13:45
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6316db4 to 6f89a93 Compare July 16, 2024 07:47
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6f89a93 to 780a5e0 Compare July 23, 2024 08:05
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 780a5e0 to d0652eb Compare July 24, 2024 04:25
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d0652eb to 812f080 Compare August 9, 2024 08:18
kongponents-bot
kongponents-bot previously approved these changes Aug 9, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 812f080 to e182942 Compare August 14, 2024 05:12
@renovate renovate bot requested a review from portikM as a code owner August 14, 2024 05:12
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e182942 to 9cc75c6 Compare September 2, 2024 04:06
@adamdehaven adamdehaven deleted the renovate/major-semantic-release-monorepo branch September 24, 2024 00:39
Copy link
Contributor Author

renovate bot commented Sep 24, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 24.x releases. But if you manually upgrade to 24.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

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.

2 participants