-
Notifications
You must be signed in to change notification settings - Fork 66
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: drop node 16 and add node 22 to CI matrix MONGOSH-1898 #2255
base: main
Are you sure you want to change the base?
Conversation
Yeah, if we don't test it, it's probably best to bump it 👍 |
packages/e2e-tests/test/e2e.spec.ts
Outdated
) { | ||
// This test fails on Windows with node 22 likely due to https://github.com/nodejs/node/issues/51766 | ||
return this.skip(); | ||
} |
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.
Hm, this might be something we want to track in our own JIRA? Not sure if we should consider this a blocker to adopting Node.js 22 for our official builds, but we should probably at least discuss it
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.
Agreed - was hoping to get this to a stable state and then I'll go back and compile a list of the hacks/questionable changes that we should double check on prior to merging.
TODO:
node >= 16.15.0
- should we bump that as well?reads and runs the vscode extension example playground
reads and runs code from stdin, with .end()
cannot auth when authenticationMechanism mismatches (sha1 -> sha256)
cannot auth when authenticationMechanism mismatches (sha256 -> sha1)