-
Notifications
You must be signed in to change notification settings - Fork 0
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) #279
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-semantic-release-monorepo
base: master
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
Chore
ContributorsCommit-Lint commandsYou can trigger Commit-Lint actions by commenting on this PR:
|
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
January 8, 2023 07:09
388a177
to
bda3f62
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
January 25, 2023 08:38
e738f17
to
bbbf6f9
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
February 28, 2023 08:58
bbbf6f9
to
118e62c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 18, 2023 16:07
118e62c
to
c82f870
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v20
chore(deps): update semantic-release monorepo (major)
Mar 22, 2023
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
March 24, 2023 19:45
25303a2
to
3d620a5
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
April 7, 2023 13:38
9c65658
to
69ebb3d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
April 29, 2023 00:59
d48cc6d
to
b559b76
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
6 times, most recently
from
June 3, 2023 19:46
8559c02
to
2841f9c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
June 10, 2023 00:24
741b953
to
ac1d952
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 21, 2023 02:04
ac1d952
to
b68cc63
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
July 5, 2023 01:39
6c8900d
to
ac1f761
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
April 9, 2024 22:36
a27a50d
to
f5cf3ce
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
June 5, 2024 03:11
aad262c
to
20022c6
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 22, 2024 08:15
20022c6
to
796ac96
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
July 8, 2024 14:23
348e52e
to
c3a27cb
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
July 26, 2024 01:30
05eacce
to
379a526
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
August 15, 2024 18:53
8f7a723
to
ec4610b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
August 20, 2024 22:04
ec1736e
to
c68df28
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
September 6, 2024 00:13
cca71ba
to
11753f1
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
September 15, 2024 17:14
34a420b
to
b7656fe
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
September 24, 2024 21:46
58c0021
to
fc415e6
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 27, 2024 19:18
fc415e6
to
c48d592
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
October 25, 2024 20:02
99c372d
to
5a48fe4
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 6, 2024 18:58
5a48fe4
to
c19da04
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
December 16, 2024 21:20
c19da04
to
63b842f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 3, 2025 06:46
63b842f
to
d589246
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:
9.0.2
->13.0.1
8.1.0
->11.0.1
9.0.2
->12.0.1
10.0.3
->14.0.3
19.0.5
->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
v10.0.4
Compare Source
Bug Fixes
v10.0.3
Compare Source
Reverts
v10.0.2
Compare Source
Bug Fixes
v10.0.1
Compare Source
Bug Fixes
v10.0.0
Compare Source
Code Refactoring
Features
BREAKING CHANGES
loading ESM plugins
@semantic-release/commit-analyzer
is now a native ES Module. It has named exportsfor each plugin hook (
analyzeCommits
)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
v9.2.6
Compare Source
Bug Fixes
v9.2.5
Compare Source
Bug Fixes
v9.2.4
Compare Source
Bug Fixes
v9.2.3
Compare Source
Bug Fixes
v9.2.2
Compare Source
Bug Fixes
v9.2.1
Compare Source
v9.2.0
Compare Source
Features
v9.1.0
Compare Source
Features
releaseNameTemplate
andreleaseBodyTemplate
options for customizing release body and name (#704) (9e2678c)v9.0.7
Compare Source
Bug Fixes
v9.0.6
Compare Source
Bug Fixes
v9.0.5
Compare Source
Bug Fixes
v9.0.4
Compare Source
Bug Fixes
v9.0.3
Compare Source
Bug Fixes
v9.0.2
Compare Source
Bug Fixes
v9.0.1
Compare Source
Bug Fixes
v9.0.0
Compare Source
BREAKING CHANGES
@semantic-release/github
is now a native ES Modulesemantic-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
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
Bug Fixes
v10.0.2
Compare Source
Bug Fixes
v10.0.1
Compare Source
Bug Fixes
v10.0.0
Compare 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
errors
propertyNPM_USERNAME
andNPM_PASSWORD
is no longer supported. UseNPM_TOKEN
instead.@semantic-release/npm
is now a native ES Module. Ithas named exports for each plugin hook (
verifyConditions
,prepare
,publish
,addChannel
)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
v11.0.7
Compare Source
Bug Fixes
v11.0.6
Compare Source
Reverts
v11.0.5
Compare Source
Bug Fixes
v11.0.4
Compare Source
Bug Fixes
v11.0.3
Compare Source
Bug Fixes
v11.0.2
Compare Source
Bug Fixes
v11.0.1
Compare Source
Bug Fixes
v11.0.0
Compare Source
Code Refactoring
Features
BREAKING CHANGES
@semantic-release/release-notes-generator
is now a native ES Module. It hasnamed exports for each plugin hook (
generateNotes
)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
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 was generated by Mend Renovate. View the repository job log.