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

fix(deps): update semantic-release monorepo (major) #150

Merged
merged 2 commits into from
Aug 10, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 1, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/commit-analyzer 12.0.0 -> 13.0.0 age adoption passing confidence
@semantic-release/release-notes-generator 13.0.0 -> 14.0.1 age adoption passing confidence
semantic-release 23.1.1 -> 24.0.0 age adoption passing confidence

Release Notes

semantic-release/commit-analyzer (@​semantic-release/commit-analyzer)

v13.0.0

Compare Source

Bug Fixes
  • log the raw message again (e2f5d6c)
Features
  • support latest conventional-changelog packages (0254d7a)
BREAKING CHANGES
  • by supporting the latest major versions of conventional-changelog packages, we are
    dropping support for previous major versions of those packages due to the breaking changes between
    majors. this only impacts your project if you are installing alongside semantic-release, so updating
    those packages to latest version should be the only change you need for this update. no action
    should be necessary if you are using default semantic-release config
semantic-release/release-notes-generator (@​semantic-release/release-notes-generator)

v14.0.1

Compare Source

Bug Fixes

v14.0.0

Compare Source

Features
BREAKING CHANGES
  • by supporting the latest major versions of conventional-changelog packages, we are dropping support for previous major versions of those packages due to the breaking changes between majors. this only impacts your project if you are installing alongside semantic-release, so updating those packages to latest version should be the only change you need for this update. no action should be necessary if you are using default semantic-release config
semantic-release/semantic-release (semantic-release)

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 is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 added the dependency label Jun 1, 2024
Copy link
Member

@kayman-mk kayman-mk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved automated PR

Copy link
Contributor

github-actions bot commented Jun 1, 2024

Hey @renovate[bot]!

👋Thank you for your contribution to the project. Please refer to the contribution rules for a quick overview of the process.

Make sure that this PR clearly explains:

  • the problem being solved
  • the best way a reviewer and you can test your changes

With submitting this PR you confirm that you hold the rights of the code added and agree that it will published under the Apache 2.0 license.

This message was generated automatically. You are welcome to improve it._

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from e71c791 to 42ac2bb Compare June 7, 2024 19:08
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 42ac2bb to 339add7 Compare June 22, 2024 07:18
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 2615b29 to fba627f Compare July 8, 2024 19:07
Copy link

@HapagLloydTechnicalUser HapagLloydTechnicalUser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved automated PR

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from fba627f to a6bc5c4 Compare July 12, 2024 18:19
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from d9ef02a to 2849171 Compare July 26, 2024 06:54
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 2849171 to 714d0d8 Compare August 10, 2024 01:36
@kayman-mk kayman-mk merged commit 6f5a851 into main Aug 10, 2024
14 checks passed
@kayman-mk kayman-mk deleted the renovate/major-semantic-release-monorepo branch August 10, 2024 15:31
@HapagLloydTechnicalUser

🎉 This issue has been resolved in version 1.12.21 🎉

The release is available on:

Your semantic-release bot 📦🚀

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