chore(deps): update semantic-release monorepo (major) #196
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^9.0.1->^13.0.0^8.0.1->^13.0.0^10.0.2->^14.0.0^18.0.0->^25.0.0Release Notes
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)semantic-release/npm (@semantic-release/npm)
v13.1.2Compare Source
Bug Fixes
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]
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)semantic-release/semantic-release (semantic-release)
v25.0.2Compare Source
Bug Fixes
v25.0.1Compare Source
Bug Fixes
v25.0.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
v24.2.9Compare Source
Bug Fixes
v24.2.8Compare Source
Bug Fixes
v24.2.7Compare Source
Performance Improvements
v24.2.6Compare Source
Bug Fixes
v24.2.5Compare Source
Bug Fixes
marked-terminal(#3742) (fb1ccd4)v24.2.4Compare Source
Bug Fixes
v24.2.3Compare Source
Bug Fixes
v24.2.2Compare Source
Bug Fixes
v24.2.1Compare Source
Bug Fixes
v24.2.0Compare Source
Features
v24.1.3Compare Source
Bug Fixes
v24.1.2Compare Source
Bug Fixes
@semantic-release/githubtov11.0.0(#3460) (43df51b)v24.1.1Compare Source
Bug Fixes
v24.1.0Compare Source
Features
warntype to globalcontext.logger(#3423) (bcc663c)v24.0.0Compare Source
Bug Fixes
BREAKING CHANGES
conventional-changelog packages. if you are installing any of these packages in addition to
semantic-release, be sure to update them as well
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
v23.1.1Compare Source
Bug Fixes
v23.1.0Compare Source
Features
v23.0.8Compare Source
Bug Fixes
v23.0.7Compare Source
Bug Fixes
v23.0.6Compare Source
Bug Fixes
v23.0.5[Compare Source](https://redirect.github.com/semantic-release/semantic-relea
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.