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) #198
Conversation
0396b01
to
e8622bd
Compare
4e537a2
to
ae2cf0f
Compare
55bc7df
to
f031bb9
Compare
f031bb9
to
3a29555
Compare
28bb303
to
ae1c888
Compare
b28c8a2
to
ad4178b
Compare
7a325c7
to
481f163
Compare
68a47a2
to
9f98cac
Compare
8f63b53
to
bf6b489
Compare
bf6b489
to
42020bd
Compare
42020bd
to
0eb5eda
Compare
619f26a
to
27c7ceb
Compare
27c7ceb
to
5a59515
Compare
f0daa22
to
ad499e1
Compare
101209c
to
2a96bb4
Compare
|
If we bump the major versions of semantic release and/or the plugins, should this become a major version bump? |
|
Yeah, good question. There are breaking changes in the npm plugin that would impact consumers. The breakages from the others are due to the esm change, but those shouldn't have consumer impact since the current version already depends on the esm version of core. Because of the npm breakages, I agree that this should be considered breaking. |
3863cf6
to
912db3c
Compare
BREAKING CHANGE: This version pulls in a new major version of the NPM plugin with breaking changes. See https://github.com/semantic-release/npm/releases/tag/v10.0.0 for details.
912db3c
to
6e28163
Compare
|
Thanks for the feedback. I added the breaking change trailer with a link to the NPM plugin release notes. |
|
🎉 This PR is included in version 12.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This PR contains the following updates:
^11.0.0->^12.0.0^9.0.0->^10.0.0^10.0.2->^11.0.020.1.3->21.0.2Release Notes
semantic-release/gitlab
v12.0.1Compare Source
Bug Fixes
v12.0.0Compare Source
Bug Fixes
BREAKING CHANGES
semantic-release/npm
v10.0.3Compare Source
Bug Fixes
v10.0.2Compare Source
Bug Fixes
v10.0.1Compare Source
Bug Fixes
v10.0.0Compare Source
Bug Fixes
Code Refactoring
Features
BREAKING CHANGES
can be found at https://github.com/npm/cli/releases/tag/v9.0.0
raised to v20.1.0 in order to support loading of ESM plugins
errorspropertyNPM_USERNAMEandNPM_PASSWORDis no longer supported. UseNPM_TOKENinstead.@semantic-release/npmis now a native ES Module. Ithas named exports for each plugin hook (
verifyConditions,prepare,publish,addChannel)semantic-release/release-notes-generator
v11.0.1Compare Source
Bug Fixes
v11.0.0Compare Source
Code Refactoring
Features
BREAKING CHANGES
@semantic-release/release-notes-generatoris now a native ES Module. It hasnamed exports for each plugin hook (
generateNotes)semantic-release/semantic-release
v21.0.2Compare Source
Bug Fixes
v21.0.1Compare Source
Bug Fixes
v21.0.0Compare Source
BREAKING CHANGES
NPM_USERNAMEandNPM_PASSWORDis no longer supported. UseNPM_TOKENinstead.Bug Fixes
@semantic-release/npmto^10.0.0(d647433)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.