fix(deps): update semantic-release monorepo (major) #332
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
36f4919
to
6415a8e
Compare
|
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 |
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
6415a8e
to
93c6223
Compare
|
fgreinacher
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
9214907
to
9b027d5
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
9b027d5
to
9431c57
Compare
The new semantic-release version adds support for the latest conventional-changelog packages BREAKING CHANGE: 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
Edited/Blocked NotificationRenovate 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. |
|
I have pushed eb8fcf1 to bump the peer dependency and included a breaking change trailer. |
This PR contains the following updates:
^12.0.0->^13.0.0^13.0.0->^14.0.023.1.1->24.0.0Release Notes
semantic-release/commit-analyzer (@semantic-release/commit-analyzer)
v13.0.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
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.0Compare Source
Features
BREAKING CHANGES
semantic-release/semantic-release (semantic-release)
v24.0.0Compare Source
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.
This PR has been generated by Mend Renovate. View repository job log here.