-
-
Notifications
You must be signed in to change notification settings - Fork 2
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) #21
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate_major-semantic-release-monorepo
base: main
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@semantic-release/commit-analyzer@10.0.4, npm/@semantic-release/github@9.2.6, npm/@semantic-release/npm@10.0.6, npm/@semantic-release/release-notes-generator@11.0.7, npm/semantic-release@21.1.2 |
renovate
bot
changed the title
fix(deps): update dependency @semantic-release/npm to v11
fix(deps): update semantic-release monorepo (major)
Sep 17, 2023
renovate
bot
force-pushed
the
renovate_major-semantic-release-monorepo
branch
4 times, most recently
from
September 24, 2023 00:50
3c7392b
to
d6aa866
Compare
renovate
bot
force-pushed
the
renovate_major-semantic-release-monorepo
branch
from
September 25, 2023 17:08
d6aa866
to
114261c
Compare
renovate
bot
force-pushed
the
renovate_major-semantic-release-monorepo
branch
2 times, most recently
from
November 4, 2023 21:22
d655814
to
a53a980
Compare
renovate
bot
force-pushed
the
renovate_major-semantic-release-monorepo
branch
from
November 18, 2023 03:38
a53a980
to
313b1f8
Compare
renovate
bot
force-pushed
the
renovate_major-semantic-release-monorepo
branch
3 times, most recently
from
December 13, 2023 00:17
0593bee
to
b767584
Compare
renovate
bot
force-pushed
the
renovate_major-semantic-release-monorepo
branch
from
December 13, 2023 06:55
b767584
to
44bb3f3
Compare
renovate
bot
force-pushed
the
renovate_major-semantic-release-monorepo
branch
from
January 13, 2024 22:52
44bb3f3
to
cdad527
Compare
renovate
bot
force-pushed
the
renovate_major-semantic-release-monorepo
branch
2 times, most recently
from
February 8, 2024 15:22
133321f
to
6b35c8e
Compare
renovate
bot
force-pushed
the
renovate_major-semantic-release-monorepo
branch
5 times, most recently
from
March 19, 2024 15:00
fc5022b
to
2ea7b55
Compare
renovate
bot
force-pushed
the
renovate_major-semantic-release-monorepo
branch
2 times, most recently
from
March 25, 2024 16:02
4a0f0b8
to
920c970
Compare
renovate
bot
force-pushed
the
renovate_major-semantic-release-monorepo
branch
2 times, most recently
from
April 11, 2024 00:13
a292478
to
9d15a48
Compare
renovate
bot
force-pushed
the
renovate_major-semantic-release-monorepo
branch
from
May 11, 2024 20:08
9d15a48
to
3443420
Compare
renovate
bot
force-pushed
the
renovate_major-semantic-release-monorepo
branch
from
June 2, 2024 01:33
3443420
to
e6751c3
Compare
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:
^10.0.0
->^13.0.0
^9.0.0
->^10.0.0
^10.0.0
->^12.0.0
^11.0.0
->^14.0.0
21.1.2
->24.0.0
Release Notes
semantic-release/commit-analyzer (@semantic-release/commit-analyzer)
v13.0.0
Compare 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.0
Compare Source
Features
exports
to point at ./index.js (f3358dd)BREAKING CHANGES
exports
has been defined, which prevents access to private apis (which arentintended for consumption anyway)
v11.1.0
Compare Source
Features
v11.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
semantic-release/github (@semantic-release/github)
v10.0.5
Compare Source
Bug Fixes
v10.0.4
Compare Source
Bug Fixes
v10.0.3
Compare Source
v10.0.2
Compare Source
Bug Fixes
v10.0.1
Compare Source
Bug Fixes
v10.0.0
Compare Source
Features
BREAKING CHANGES
semantic-release/npm (@semantic-release/npm)
v12.0.1
Compare Source
Bug Fixes
v12.0.0
Compare Source
Features
exports
to point at ./index.js (9e193c2)BREAKING CHANGES
exports
has been defined, which prevents access to private apis (which arentintended for consumption anyway)
v11.0.3
Compare 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.2
Compare Source
Bug Fixes
v11.0.1
Compare Source
Bug Fixes
v11.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
semantic-release/release-notes-generator (@semantic-release/release-notes-generator)
v14.0.0
Compare Source
Features
BREAKING CHANGES
v13.0.0
Compare Source
Features
exports
to point at ./index.js (5655b18)BREAKING CHANGES
exports
has been defined, which prevents access to private apis (which arentintended for consumption anyway)
v12.1.0
Compare Source
Features
v12.0.1
Compare Source
Bug Fixes
v12.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
semantic-release/semantic-release (semantic-release)
v24.0.0
Compare Source
v23.1.1
Compare Source
v23.1.0
Compare Source
v23.0.8
Compare Source
Bug Fixes
v23.0.7
Compare Source
v23.0.6
Compare Source
Bug Fixes
v23.0.5
Compare Source
v23.0.4
Compare Source
v23.0.3
Compare Source
v23.0.2
Compare Source
Bug Fixes
v23.0.1
Compare Source
Bug Fixes
v23.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
https://github.com/semantic-release/env-ci/releases/tag/v11.0.0 for more information
related to https://github.com/semantic-release/semantic-release/discussions/3088
release.config.js
as the name of your config file, it needs to be moved to a.config/
directory. see https://github.com/cosmiconfig/cosmiconfig/releases/tag/v9.0.0 for more detailv22.0.12
Compare Source
Bug Fixes
v22.0.11
Compare Source
Bug Fixes
v22.0.10
Compare Source
Bug Fixes
v22.0.9
Compare Source
Bug Fixes
v22.0.8
Compare Source
Bug Fixes
v22.0.7
Compare Source
Bug Fixes
Features
v22.0.6
Compare Source
Bug Fixes
v22.0.5
Compare Source
Bug Fixes
v22.0.4
Compare Source
Bug Fixes
v22.0.3
Compare Source
Bug Fixes
exports
definition for the time being (561e2d6), closes #2968. see https://github.com/semantic-release/semantic-release/issues/2978 for more information.v22.0.2
Compare Source
Bug Fixes
v22.0.1
Compare Source
Bug Fixes
release-notes-generator
andcommit-analyzer
plugins to stable versions (041e4f7), closes #2934v22.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
v20.6.1 to avoid a known node bug
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.