-
Couldn't load subscription status.
- Fork 7
chore(deps): update semantic-release monorepo (major) #16
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
base: main
Are you sure you want to change the base?
Conversation
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: package-lock.json |
19a55e1 to
fc26682
Compare
eb6dfc1 to
733c762
Compare
733c762 to
b5a2a75
Compare
b5a2a75 to
a2d780c
Compare
|
2c6afe7 to
5e8886d
Compare
5e8886d to
29ce798
Compare
This PR contains the following updates:
^5.0.1->^6.0.0^8.0.1->^13.0.0^9.0.1->^10.0.0^7.1.3->^13.0.0^9.0.3->^14.0.0Release Notes
semantic-release/changelog (@semantic-release/changelog)
v6.0.3Compare Source
Bug Fixes
v6.0.2Compare Source
Bug Fixes
v6.0.1Compare Source
Bug Fixes
v6.0.0Compare Source
Features
BREAKING CHANGES
semantic-release/commit-analyzer (@semantic-release/commit-analyzer)
v13.0.1Compare Source
Bug Fixes
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
v12.0.0Compare Source
Features
exportsto point at ./index.js (f3358dd)BREAKING CHANGES
exportshas been defined, which prevents access to private apis (which arentintended for consumption anyway)
v11.1.0Compare Source
Features
v11.0.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
v10.0.4Compare Source
Bug Fixes
v10.0.3Compare Source
Reverts
v10.0.2Compare Source
Bug Fixes
v10.0.1Compare Source
Bug Fixes
v10.0.0Compare Source
Code Refactoring
Features
BREAKING CHANGES
loading ESM plugins
@semantic-release/commit-analyzeris now a native ES Module. It has named exportsfor each plugin hook (
analyzeCommits)v9.0.2Compare Source
Bug Fixes
v9.0.1Compare Source
Bug Fixes
v9.0.0Compare Source
Features
BREAKING CHANGES
semantic-release/git (@semantic-release/git)
v10.0.1Compare Source
Bug Fixes
v10.0.0Compare Source
Features
BREAKING CHANGES
semantic-release/npm (@semantic-release/npm)
v13.1.1Compare Source
Bug Fixes
v13.1.0Compare Source
Features
Bug Fixes
v13.0.0Compare Source
Features
Bug Fixes
BREAKING CHANGES
v12.0.2Compare Source
Bug Fixes
v12.0.1Compare Source
Bug Fixes
v12.0.0Compare Source
Features
exportsto point at ./index.js (9e193c2)BREAKING CHANGES
exportshas been defined, which prevents access to private apis (which arentintended for consumption anyway)
v11.0.3Compare Source
Bug Fixes
even though our existing range allowed anyone to update as soon as the new npm version was available, this will encourage being on a version that does not report the ip vulnerability a bit more forcefully
v11.0.2Compare Source
Bug Fixes
v11.0.1Compare Source
Bug Fixes
v11.0.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
v10.0.6Compare Source
Bug Fixes
v10.0.5Compare Source
Bug Fixes
v10.0.4Compare Source
Bug Fixes
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)v9.0.2Compare Source
Bug Fixes
v9.0.1Compare Source
Bug Fixes
preferLocaloption for execa call (#458) (c817a88)v9.0.0Compare Source
Bug Fixes
preferLocaloption to allow execa to use local npm version (#445) (002439e)semantic-releaseto the new stable version (575a5a4)semantic-releaseto a version matching the engines definition of this package (2d1f5f2)BREAKING CHANGES
semantic-releasehas been raised to match theengines.noderequirements of this packageCo-authored-by: Matt Travi [email protected]
v8.0.3Compare Source
Reverts
v8.0.2Compare Source
Bug Fixes
v8.0.1Compare Source
Bug Fixes
v8.0.0Compare Source
Features
BREAKING CHANGES
Co-authored-by: Matt Travi [email protected]
semantic-release/release-notes-generator (@semantic-release/release-notes-generator)
v14.1.0Compare Source
Features
v14.0.3Compare Source
Bug Fixes
v14.0.2Compare Source
Bug Fixes
v14.0.1Compare Source
Bug Fixes
v14.0.0Compare Source
Features
BREAKING CHANGES
v13.0.0Compare Source
Features
exportsto point at ./index.js (5655b18)BREAKING CHANGES
exportshas been defined, which prevents access to private apis (which arentintended for consumption anyway)
v12.1.0Compare Source
Features
v12.0.1Compare Source
Bug Fixes
v12.0.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
v11.0.7Compare Source
Bug Fixes
v11.0.6Compare Source
Reverts
v11.0.5Compare Source
Bug Fixes
v11.0.4Compare Source
Bug Fixes
v11.0.3Compare Source
Bug Fixes
v11.0.2Compare Source
Bug Fixes
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)v10.0.3Compare Source
Bug Fixes
v10.0.2Compare Source
Bug Fixes
v10.0.1Compare Source
Bug Fixes
v10.0.0Compare Source
BREAKING CHANGES
Thanks
@abel-mak
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 was generated by Mend Renovate. View the repository job log.