Repository navigation
fix(deps): update semantic-release monorepo to v13 - #54
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/major-13-semantic-release-monorepo
branch
from
June 1, 2024 00:43
d129675 to
403222b
Compare
renovate
Bot
force-pushed
the
renovate/major-13-semantic-release-monorepo
branch
from
December 9, 2024 08:03
4416fa8 to
403222b
Compare
renovate
Bot
force-pushed
the
renovate/major-13-semantic-release-monorepo
branch
from
January 3, 2025 07:28
403222b to
0c8fe89
Compare
renovate
Bot
force-pushed
the
renovate/major-13-semantic-release-monorepo
branch
3 times, most recently
from
October 19, 2025 21:34
1e6200c to
377a5c7
Compare
renovate
Bot
force-pushed
the
renovate/major-13-semantic-release-monorepo
branch
from
November 14, 2025 23:45
377a5c7 to
57e5699
Compare
renovate
Bot
force-pushed
the
renovate/major-13-semantic-release-monorepo
branch
from
December 12, 2025 20:35
57e5699 to
a609ea7
Compare
renovate
Bot
force-pushed
the
renovate/major-13-semantic-release-monorepo
branch
from
February 6, 2026 21:36
a609ea7 to
0dd4226
Compare
renovate
Bot
force-pushed
the
renovate/major-13-semantic-release-monorepo
branch
from
March 1, 2026 20:45
0dd4226 to
af3ef49
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
Bot
force-pushed
the
renovate/major-13-semantic-release-monorepo
branch
from
September 21, 2026 22:57
af3ef49 to
0ca47ed
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
8.0.1→13.0.17.0.5→13.2.09.0.1→13.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)v9.0.2Compare Source
Bug Fixes
v9.0.1Compare Source
Bug Fixes
v9.0.0Compare Source
Features
BREAKING CHANGES
semantic-release/npm (@semantic-release/npm)
v13.2.0Compare Source
Features
v13.1.5Compare Source
Bug Fixes
v13.1.4Compare Source
Bug Fixes
v13.1.3Compare Source
Bug Fixes
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 programmer@travi.org
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 programmer@travi.org
v7.1.3Compare Source
Bug Fixes
v7.1.2Compare Source
Bug Fixes
v7.1.1Compare Source
Bug Fixes
v7.1.0Compare Source
Features
v7.0.10Compare Source
Bug Fixes
v7.0.9Compare Source
Bug Fixes
v7.0.8Compare Source
Bug Fixes
v7.0.7Compare Source
Bug Fixes
v7.0.6Compare Source
Bug Fixes
semantic-release/release-notes-generator (@semantic-release/release-notes-generator)
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
v9.0.3Compare Source
Bug Fixes
v9.0.2Compare Source
Bug Fixes
Configuration
📅 Schedule: (in timezone America/New_York)
* 0-3 * * *)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.