-
Notifications
You must be signed in to change notification settings - Fork 2k
Fix test failure with Node 18.20.3 #7898
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
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
Our CI installs the latest version associated with a given Node version, so it started to fail when this started loading v18.20.3 which reverted the change backported to v18.19.
0ec5868
to
543db82
Compare
✅ Deploy Preview for apollo-server-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
// | ||
// (Node 18.19.0 had this change backported but it was removed again in | ||
// 18.20.3; our tests only pin major versions so we can assume 18 means | ||
// >= 18.20.3.) Update: Node 18.19+ had this change backported, so the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops, didn't delete the end of the comment
✅ Deploy Preview for apollo-server-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Our CI installs the latest version associated with a given Node version, so it started to fail when this started loading v18.20.3 which reverted the change backported to v18.19.
Our CI installs the latest version associated with a given Node version, so it started to fail when this started loading v18.20.3 which reverted the change backported to v18.19.