Update dependency babel-merge to v2 #1002
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
There may be a couple changes to make from this, but possibly not. I'm going to wait on a README update by the original patch author before moving forward on this. |
PR has been editedAs this PR has been edited, Renovate will stop updating it in order to not cause any conflicts or other problems. If you wish to abandon your edits and have Renovate recreate this PR then you should rename this PR and then close it. |
|
@eliperelman is this good to merge after a rebase? To clarify - the change in merge behaviour is breaking, but not in a way that means we need to update anything in this repo, right? :-) |
eliperelman
force-pushed
the
renovate/babel-merge-2.x
branch
from
582acf1 to
ba9145f
Compare
|
@edmorley I believe so; I went through all of our usages of |
Renovate Ignore NotificationAs this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 2.x releases. However, if you upgrade to 2.x manually then Renovate will then reenable updates for minor and patch updates automatically. If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened. |
|
wtf |
|
omfg |
|
Give the branch a new name for now and I'll file an issue against Renovate. |
|
(Renovate has a "check if a human has edited a branch, and if so stop touching it" feature, which might have been confused by the force push rebase) |
|
Interesting. Yeah I opened a new branch, just waiting on CI. 😜 |
This Pull Request updates dependency babel-merge from
^1.1.1to^2.0.0Release Notes
v2.0.0Compare Source
This PR has been generated by Renovate Bot.