-
Notifications
You must be signed in to change notification settings - Fork 19
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) #286
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
from
January 9, 2020 20:02
22263b2
to
68108e7
Compare
renovate
bot
changed the title
chore(deps): update dependency @semantic-release/git to v8
chore(deps): update semantic-release monorepo (major)
Jan 9, 2020
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
January 15, 2020 18:52
5b85110
to
08a8dcd
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
9 times, most recently
from
January 28, 2020 16:42
169a488
to
0de9274
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
6 times, most recently
from
February 7, 2020 15:28
5e1ec21
to
769b9ce
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
February 13, 2020 01:06
3150fd6
to
21e9984
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
February 20, 2020 21:41
4979c10
to
739b5af
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 9, 2020 15:35
739b5af
to
e358ea2
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 19, 2020 15:56
e358ea2
to
b3b67d0
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 9, 2023 20:02
b04072d
to
e5567b7
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 29, 2023 21:10
e5567b7
to
35f7fab
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
December 7, 2023 19:15
35f7fab
to
74963e5
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
December 22, 2023 21:21
74963e5
to
e5fac7d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 2, 2024 01:04
e5fac7d
to
51d875f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
March 16, 2024 04:59
7775165
to
4d967b1
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
April 6, 2024 23:37
4d967b1
to
49c8b0b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
May 16, 2024 04:21
a3249df
to
e2c3415
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 22, 2024 19:05
e2c3415
to
c8e011c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 5, 2024 02:05
c8e011c
to
8053a0e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
July 8, 2024 14:24
d0241e0
to
9a0b877
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
July 26, 2024 01:19
593845e
to
66b671e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
August 15, 2024 21:52
c21c676
to
7172f0b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
August 20, 2024 20:01
7172f0b
to
51a7a22
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
September 6, 2024 02:09
56cb800
to
bd9dd3c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
September 20, 2024 20:19
ea52bcc
to
0b867e6
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 24, 2024 22:19
0b867e6
to
576899b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 6, 2024 18:38
576899b
to
6b22e88
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:
3.0.6
->6.0.3
7.0.18
->10.0.1
5.5.8
->11.0.1
5.3.5
->12.0.1
Release Notes
semantic-release/changelog (@semantic-release/changelog)
v6.0.3
Compare Source
Bug Fixes
v6.0.2
Compare Source
Bug Fixes
v6.0.1
Compare Source
Bug Fixes
v6.0.0
Compare Source
Features
BREAKING CHANGES
v5.0.1
Compare Source
Bug Fixes
v5.0.0
Compare Source
chore
BREAKING CHANGES
v4.0.0
Compare Source
Features
BREAKING CHANGES
semantic-release/git (@semantic-release/git)
v10.0.1
Compare Source
Bug Fixes
v10.0.0
Compare Source
Features
BREAKING CHANGES
v9.0.1
Compare Source
Bug Fixes
v9.0.0
Compare Source
chore
BREAKING CHANGES
v8.0.0
Compare Source
Bug Fixes
Features
branch
parameter from [email protected] (02b1f6d)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
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
v8.0.6
Compare Source
Bug Fixes
v8.0.5
Compare Source
Bug Fixes
v8.0.4
Compare Source
Bug Fixes
v8.0.3
Compare Source
Bug Fixes
v8.0.2
Compare Source
Bug Fixes
v8.0.1
Compare Source
Bug Fixes
v8.0.0
Compare Source
BREAKING CHANGES
v7.2.3
Compare Source
Bug Fixes
v7.2.2
Compare Source
Bug Fixes
v7.2.1
Compare Source
Bug Fixes
v7.2.0
Compare Source
Features
v7.1.2
Compare Source
Bug Fixes
v7.1.1
Compare Source
Bug Fixes
v7.1.0
Compare Source
Features
v7.0.7
Compare Source
Bug Fixes
v7.0.6
Compare Source
Bug Fixes
v7.0.5
Compare Source
Bug Fixes
v7.0.4
Compare Source
Bug Fixes
v7.0.3
Compare Source
Bug Fixes
v7.0.2
Compare Source
Bug Fixes
@octokit/rest
deprecations (#249) (c1ae4ac)v7.0.1
Compare Source
Bug Fixes
v7.0.0
Compare Source
chore
BREAKING CHANGES
v6.0.2
Compare Source
Bug Fixes
v6.0.1
Compare Source
Bug Fixes
v6.0.0
Compare Source
Bug Fixes
branch.main
flag to determine is the release need theprerelease
flag (7aaeb0f)context.branch
(5f19284)Features
addChannel
plugin step (589a5c4)nextRelease.channel
property inpublish
step (869c827)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
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
v9.0.1
Compare Source
Bug Fixes
preferLocal
option for execa call (#458) (c817a88)v9.0.0
Compare Source
Bug Fixes
preferLocal
option to allow execa to use local npm version (#445) (002439e)semantic-release
to the new stable version (575a5a4)semantic-release
to a version matching the engines definition of this package (2d1f5f2)BREAKING CHANGES
semantic-release
has been raised to match theengines.node
requirements of this packageCo-authored-by: Matt Travi [email protected]
v8.0.3
Compare Source
Reverts
v8.0.2
Compare Source
Bug Fixes
v8.0.1
Compare Source
Bug Fixes
v8.0.0
Compare Source
Features
BREAKING CHANGES
Co-authored-by: Matt Travi [email protected]
v7.1.3
Compare Source
Bug Fixes
v7.1.2
[Compare Source](https://
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.