chore(deps): update semantic-release monorepo - #650
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/semantic-release-monorepo
branch
from
November 10, 2025 19:33
a3fba28 to
2da07e9
Compare
renovate
Bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
December 3, 2025 18:30
2da07e9 to
cec7ac6
Compare
renovate
Bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
February 12, 2026 16:30
cec7ac6 to
c9a32f7
Compare
renovate
Bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
March 5, 2026 14:09
c9a32f7 to
7b12bbc
Compare
renovate
Bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
March 13, 2026 18:47
7b12bbc to
09f8b2e
Compare
renovate
Bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
April 1, 2026 18:47
09f8b2e to
f3235bd
Compare
renovate
Bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
May 12, 2026 11:32
f3235bd to
738fd15
Compare
renovate
Bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
June 11, 2026 18:43
738fd15 to
04b52ae
Compare
renovate
Bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
July 12, 2026 12:05
04b52ae to
ff68807
Compare
renovate
Bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
July 30, 2026 20:16
ff68807 to
2b9d4cf
Compare
renovate
Bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
September 2, 2026 20:48
2b9d4cf to
784cc59
Compare
Contributor
Author
|
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:
11.0.2→11.0.323.0.2→23.1.1Release Notes
semantic-release/npm (@semantic-release/npm)
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
semantic-release/semantic-release (semantic-release)
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.5Compare Source
Bug Fixes
v23.0.4Compare Source
Bug Fixes
v23.0.3Compare Source
Bug Fixes
Configuration
📅 Schedule: (UTC)
🚦 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.