-
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): semantic-release monorepo (major) #269
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 }}
Could not load tags
Nothing to show
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
2 times, most recently
from
January 22, 2020 18:24
df6c213
to
b07f6e5
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
6 times, most recently
from
January 31, 2020 16:26
f9e090e
to
d5f9dc9
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
February 17, 2020 19:16
1ea5dcc
to
37a21f3
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
March 30, 2020 09:55
6e16b26
to
537d69d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
5 times, most recently
from
April 16, 2020 21:55
6afee0e
to
5556892
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
April 27, 2020 09:45
ded2786
to
532deb4
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
May 11, 2020 10:50
f1dc302
to
d033dfa
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 24, 2020 20:32
d033dfa
to
5a96582
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
June 25, 2020 16:44
ed27c41
to
61f6b05
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 28, 2020 17:01
61f6b05
to
2181e52
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 28, 2020 11:52
2181e52
to
617d819
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 23, 2021 03:59
617d819
to
6a9711e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
April 12, 2021 18:34
6a9711e
to
a5c39d3
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 10, 2021 02:35
a5c39d3
to
b813253
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 24, 2021 09:39
b813253
to
fe1d66e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 5, 2021 03:56
fe1d66e
to
365e089
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
September 21, 2021 20:58
06c448f
to
e18d334
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 30, 2021 08:58
e18d334
to
f943557
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
December 15, 2021 20:57
f943557
to
d69ce3a
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
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:
3.3.8
->6.0.3
7.0.18
->10.0.1
Release Notes
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
v5.0.0
Compare Source
chore
BREAKING CHANGES
v4.0.0
Compare Source
Bug Fixes
false
inaddChannel
if step is skipped (d12a029)false
inpublish
if package if step is skipped (48fc813)Features
addChannel
plugin step (bdeda6c)BREAKING CHANGES
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 semantic-release@16.0.0 (02b1f6d)BREAKING CHANGES
Configuration
📅 Schedule: Branch creation - "every weekend" in timezone America/Los_Angeles, 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 has been generated by Mend Renovate. View repository job log here.