-
Notifications
You must be signed in to change notification settings - Fork 1
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) #30
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
from
March 21, 2023 22:33
b09170f
to
454ea91
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 20:38
07a30f1
to
a110e62
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
April 7, 2023 13:32
d2f007a
to
643ee49
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
April 28, 2023 22:58
643ee49
to
2affe5f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
June 8, 2023 03:26
21d185b
to
114e345
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 10, 2023 01:31
114e345
to
30b4efd
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 28, 2023 22:04
30b4efd
to
e1b7fea
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
July 16, 2023 03:32
aae25b7
to
bb7835a
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
5 times, most recently
from
August 24, 2023 17:33
60f03e5
to
cf96e68
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
September 16, 2023 08:42
a7699cc
to
e20a010
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
September 23, 2023 13:39
2ee7af7
to
43363ad
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
September 27, 2023 01:12
790f21f
to
1c8b260
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
April 9, 2024 21:54
026925c
to
75db4e9
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
May 16, 2024 04:18
f15536d
to
618b324
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 22, 2024 19:25
618b324
to
1b7e789
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
June 5, 2024 01:42
267e8b2
to
eafc641
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
July 8, 2024 14:14
6590b1b
to
9a1eaa1
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
July 26, 2024 03:41
5f84cca
to
c0cc62d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
August 15, 2024 23:08
a4f7430
to
a8e3c5d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
August 20, 2024 23:07
473a9fa
to
73218f4
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
5 times, most recently
from
September 6, 2024 01:18
b318e7c
to
6a9c8d6
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
September 15, 2024 16:49
01f0d9c
to
4d811cb
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
September 27, 2024 17:08
f2c5145
to
26771e1
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 18, 2024 23:00
26771e1
to
bf15d2c
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:
8.0.6
->11.0.0
9.0.1
->12.0.1
19.0.5
->24.1.3
Release Notes
semantic-release/github (@semantic-release/github)
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 Modulev8.1.0
Compare Source
Features
v8.0.9
Compare Source
Bug Fixes
v8.0.8
Compare Source
Bug Fixes
v8.0.7
Compare Source
Bug Fixes
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
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
)v9.0.2
Compare Source
Bug Fixes
semantic-release/semantic-release (semantic-release)
v24.1.3
Compare Source
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
v21.1.2
Compare Source
Bug Fixes
v21.1.1
Compare Source
Bug Fixes
v21.1.0
Compare Source
Features
v21.0.9
Compare Source
Bug Fixes
v21.0.8
Compare Source
Bug Fixes
v21.0.7
Compare Source
Bug Fixes
v21.0.6
Compare Source
Bug Fixes
v21.0.5
Compare Source
Bug Fixes
v21.0.4
Compare Source
Bug Fixes
v21.0.3
Compare Source
Bug Fixes
@semantic-release/commit-analyzer
tov10.0.0-beta.1
(4a6b31f)@semantic-release/github
to9.0.0-beta.2
(#2818) (6f19d77)v21.0.2
Compare Source
Bug Fixes
v21.0.1
Compare Source
Bug Fixes
v21.0.0
Compare Source
BREAKING CHANGES
NPM_USERNAME
andNPM_PASSWORD
is no longer supported. UseNPM_TOKEN
instead.Bug Fixes
@semantic-release/npm
to^10.0.0
(d647433)v20.1.3
Compare Source
Bug Fixes
v20.1.2
Compare Source
Bug Fixes
v20.1.1
Compare Source
Bug Fixes
v20.1.0
Compare Source
Features
v20.0.4
Compare Source
Bug Fixes
v20.0.3
Compare Source
Reverts
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.