-
Notifications
You must be signed in to change notification settings - Fork 150
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.js v14.x failures #797
Comments
|
I have to publish a new version, and I have to have an unbreakable commitment from the build team that v14.0.0 will be the first version in which |
@ljharb, v14.x is due to be released Tuesday 21st April containing nodejs/node#31553 (I don't want to say unbreakable commitment, but there are no plans to back this PR out of v14.x.) |
We do have nodejs/package-maintenance#261 open in package-maintenance - but a little unsure on what are the steps that need to be taken here? How can I help? |
@BethGriggs v1.16.0 of resolve now considers |
This issue is fairly stale and I believe each of the failures have been addressed. |
Raising this issue to cover failures and flakes for Node.js 14.
https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/2314/testReport/
All platforms
Multiple
The text was updated successfully, but these errors were encountered: