-
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) #477
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
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
10 times, most recently
from
September 27, 2021 20:12
3243ae7
to
5c7c5ac
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
9 times, most recently
from
October 4, 2021 19:59
bfbde1c
to
0b42ed2
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
10 times, most recently
from
October 11, 2021 22:47
fe63786
to
222d7af
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 12, 2021 20:32
222d7af
to
fc5a746
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
11 times, most recently
from
March 6, 2022 07:39
e43c281
to
b2d3314
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
March 9, 2022 16:57
9745a2f
to
8f80a60
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 25, 2022 12:32
8f80a60
to
3b4fb62
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 20, 2022 16:47
3b4fb62
to
49aff5b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 16, 2023 13:25
49aff5b
to
ccf5f52
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 24, 2023 15:36
ccf5f52
to
60ec76c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
April 17, 2023 09:40
60ec76c
to
6c2144b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 14, 2023 12:21
6c2144b
to
53f4bfe
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
August 19, 2023 16:40
53f4bfe
to
9a2924c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
September 15, 2023 21:32
e3b882d
to
f2adf06
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 3, 2023 00:10
f2adf06
to
f8b89a4
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
December 7, 2023 18:16
f8b89a4
to
a7fa5df
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 2, 2024 20:18
a7fa5df
to
89a91c4
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 16, 2024 06:22
89a91c4
to
d531f18
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 9, 2024 17:02
d531f18
to
16a729b
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:
5.0.1
->6.0.3
5.0.0
->6.0.3
9.0.1
->10.0.1
7.1.3
->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
semantic-release/exec (@semantic-release/exec)
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
semantic-release/git (@semantic-release/git)
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
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]
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.