-
-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
node 14.0.0 #53494
node 14.0.0 #53494
Conversation
Thanks for this PR!
This depends on the in-progress (ish) #52481 for the newest version of |
👋 Haven't seen you for a veeeery long time! :) |
I was thinking that too! Hi, James! 👋 |
This comment has been minimized.
This comment has been minimized.
No, we're all volunteers here. A maintainer will get to it when they have time. |
1620075
to
d9ef24e
Compare
Rebased. Should be good to go now I think! |
It seems like |
|
|
What is typically the approach to this kind of situation? Do we just have to file issues with the other projects and wait until they've resolved downstream before the new Node can be made available? |
Could you try to bump revisions for
|
Doesn't seem to help - I'm pretty sure the projects just aren't compatible yet. Maybe they could be attached to the last LTS instead - node@12? |
Can you file an issue and change them to node@12? |
Sorry actually I think I'm mistaken. Don't really understand why it makes a difference, but bumping the revisions seemingly has fixed it :) (at least when running the upgrade & test locally) |
Yeah, that makes sense. Node 13 was v79. Revision bump is the right thing to do. |
Looks like it's good to merge :) |
@issyl0 has triggered a merge. |
Thanks again, @billinghamj! 👋 |
Created with
brew bump-formula-pr
.