-
-
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
chore(deps): update semantic-release monorepo (major) #350
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 }}
Loading
Could not load tags
Nothing to show
Loading
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
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
October 23, 2023 00:32
8871441
to
6d05255
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
October 30, 2023 04:23
df53eaa
to
534c97c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
6 times, most recently
from
November 6, 2023 08:20
1107371
to
88ed020
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
November 17, 2023 04:44
a33e04d
to
9be8739
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
November 20, 2023 07:03
e76e95d
to
952d31e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
November 27, 2023 07:28
40762d1
to
1175846
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
5 times, most recently
from
December 11, 2023 03:53
f431ade
to
7a119b5
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
December 18, 2023 04:15
86e1c95
to
b8076d9
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
January 1, 2024 03:57
519ef30
to
c1af3c4
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 1, 2024 06:02
c1af3c4
to
03de020
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
July 8, 2024 15:16
823764b
to
7cd2410
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
July 19, 2024 17:14
4c577cf
to
b09d02e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
July 26, 2024 01:12
b7886c0
to
8da9071
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
August 5, 2024 04:11
2257447
to
945322c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
August 15, 2024 20:06
9014504
to
d53960a
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
August 20, 2024 20:03
7945445
to
7021074
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
September 5, 2024 23:12
fef829a
to
12e2f5c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
September 15, 2024 19:18
ae8f137
to
38c0451
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
September 24, 2024 21:34
2bf766c
to
de53caa
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 27, 2024 19:31
de53caa
to
89dc6be
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 18, 2024 22:35
89dc6be
to
0410e99
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 25, 2024 23:07
0410e99
to
03ebc74
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 6, 2024 21:31
03ebc74
to
8bba413
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
December 16, 2024 23:43
8bba413
to
c88c920
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 3, 2025 04:41
c88c920
to
2da61ec
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.4
->13.0.1
9.2.6
->11.0.1
10.0.6
->12.0.1
11.0.7
->14.0.3
21.1.2
->24.2.1
Release Notes
semantic-release/commit-analyzer (@semantic-release/commit-analyzer)
v13.0.1
Compare Source
Bug Fixes
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)
v11.0.1
Compare Source
Bug Fixes
v11.0.0
Compare Source
chore
semantic-release
(95c7cdd)Code Refactoring
label
property data type. (718134a)Features
warn
infail
script (7a9914a)warn
insuccess
script (792720d)BREAKING CHANGES
label
prop is now an array of objects with more properties@semantic-release/github is now v24.1.0
v10.3.5
Compare Source
Bug Fixes
searchAPI
usage withGraphQL
infindSRIssue
util (#907) (7fb46a3)v10.3.4
Compare Source
v10.3.3
Compare Source
Bug Fixes
v10.3.2
Compare Source
Bug Fixes
"PullRequest".canBeRebased
field on GHES graphql api (#913) (4393578)v10.3.1
Compare Source
Bug Fixes
max_node_limit_exceeded
error when fetching associatedPRs (#912) (bb806af)v10.3.0
Compare Source
Features
v10.2.0
Compare Source
Features
v10.1.7
Compare Source
Bug Fixes
v10.1.6
Compare Source
v10.1.5
Compare Source
Bug Fixes
v10.1.4
Compare Source
Bug Fixes
v10.1.3
Compare Source
Bug Fixes
v10.1.2
Compare Source
Bug Fixes
v10.1.1
Compare Source
Bug Fixes
v10.1.0
Compare Source
Features
v10.0.7
Compare Source
Bug Fixes
v10.0.6
Compare Source
Bug Fixes
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.3
Compare Source
v14.0.2
Compare Source
Bug Fixes
v14.0.1
Compare Source
Bug Fixes
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.2.1
Compare Source
v24.2.0
Compare Source
Features
v24.1.3
Compare Source
Bug Fixes
v24.1.2
Compare Source
Bug Fixes
@semantic-release/github
tov11.0.0
(#3460) (43df51b)v24.1.1
Compare Source
v24.1.0
Compare Source
v24.0.0
Compare 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.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 - "before 5am on Monday" in timezone Europe/Warsaw, 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.