gitlab-config
gitlab-config copied to clipboard
semantic-release
fix(deps): update semantic-release monorepo (major)
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| @semantic-release/commit-analyzer | ^12.0.0 -> ^13.0.0 |
||||
| @semantic-release/release-notes-generator | ^13.0.0 -> ^14.0.0 |
||||
| semantic-release | 23.1.1 -> 24.0.0 |
Release Notes
semantic-release/commit-analyzer (@semantic-release/commit-analyzer)
v13.0.0
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.0
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
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.
👻 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 has been generated by Mend Renovate. View repository job log here.
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "Published by a pub.dev verified publisher"){kind=small}
this should be considered a breaking change and have the supported peerDependency range bumped.
as an alternative, i wonder if it makes more sense to just make semantic-release a direct dependency and drop the direct dependencies on the commit-analyzer and release-notes-generator plugins
this should be considered a breaking change and have the supported peerDependency range bumped.
as an alternative, i wonder if it makes more sense to just make semantic-release a direct dependency and drop the direct dependencies on the commit-analyzer and release-notes-generator plugins
~~Yes, this sounds like a good idea. I'll prepare a PR!~~ Just looked at this again. All other plugins are using semantic-release as peer dependency. I think we should keep this consistent to keep things easier to maintain.
Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠️ Warning: custom changes will be lost.
I have pushed https://github.com/semantic-release/gitlab-config/pull/332/commits/eb8fcf1fc0f0467f9e84f5dd6cf89fa23759ac86 to bump the peer dependency and included a breaking change trailer.