-
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) #236
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
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:54
b58a8f8
to
f8cf648
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
7 times, most recently
from
January 28, 2020 16:39
232e103
to
a9a4b2a
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
January 31, 2020 18:35
feb6e98
to
294bc35
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
February 17, 2020 19:17
021cffa
to
a25476e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 9, 2020 15:34
a25476e
to
40262d1
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 19, 2020 15:56
40262d1
to
8ecd09d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 27, 2020 05:23
8ecd09d
to
15c46ef
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
April 21, 2020 20:13
ed62d57
to
d87578e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 24, 2020 19:38
d87578e
to
fc959e3
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
July 5, 2020 09:09
b740537
to
3d6578d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 27, 2020 15:08
3d6578d
to
845ed0f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 28, 2020 10:55
845ed0f
to
bc8408e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
December 11, 2020 10:00
bc8408e
to
f7d4760
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 23, 2021 00:01
f7d4760
to
214d8de
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
February 11, 2021 14:55
214d8de
to
cae2ca0
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
March 3, 2021 22:38
26076b2
to
14fa3f0
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 13, 2021 02:16
14fa3f0
to
a2ca895
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 30, 2021 13:55
a2ca895
to
eb8817e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
April 8, 2021 17:36
eb8817e
to
ffb50d1
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
May 4, 2021 21:56
a0c279c
to
5780a2f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 14, 2021 14:18
5780a2f
to
f4cf32c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 18, 2021 17:12
f4cf32c
to
f923c6d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 7, 2022 15:37
f923c6d
to
3b9a9d7
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 29, 2022 10:27
3b9a9d7
to
a666b88
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 18, 2022 17:28
a666b88
to
0a4bad4
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 25, 2022 20:00
0a4bad4
to
231f0ec
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 17, 2023 08:03
231f0ec
to
0a93381
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 24, 2023 21:58
0a93381
to
5fe6274
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
April 17, 2023 14:15
5fe6274
to
5793209
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 9, 2023 22:21
5793209
to
cbc1d5f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
August 19, 2023 18:05
cbc1d5f
to
b07f338
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
September 15, 2023 21:43
0646a5a
to
852bc47
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 2, 2023 23:02
852bc47
to
94c366e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
December 7, 2023 19:53
94c366e
to
4b59992
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 5, 2024 20:00
4b59992
to
c0d6d1c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 2, 2024 00:09
c0d6d1c
to
811dccf
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 16, 2024 06:52
811dccf
to
36c0f0d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 9, 2024 18:32
36c0f0d
to
19e9766
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
July 25, 2024 19:43
19e9766
to
a05d618
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.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/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
Bug Fixes
v7.1.1
Compare Source
Bug Fixes
v7.1.0
Compare Source
Features
v7.0.10
Compare Source
Bug Fixes
v7.0.9
Compare Source
Bug Fixes
v7.0.8
Compare Source
Bug Fixes
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
v7.0.1
Compare Source
Bug Fixes
v7.0.0
Compare Source
chore
BREAKING CHANGES
v6.0.0
Compare Source
Bug Fixes
cwd
(a224497)false
if the npm publish is skipped (4a41228)false
inaddChannel
if package is not published on npm (5434bab)Features
addChannel
plugin step (fb96126)nextRelease.channel
property inpublish
step (b8deba7)BREAKING CHANGES
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.