-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
ci: Run tests on Node.js v16 as well as v20 #1518
base: main
Are you sure you want to change the base?
Conversation
bf90797
to
8d2794e
Compare
@takost please take a look, this should be helpful. |
8d2794e
to
eaa989f
Compare
Rebased on |
@robherley @eggyhead Would you be able to take a look? 🙏 |
eaa989f
to
2fa9ea9
Compare
👋 Hi! Thanks for the contribution. I like the idea of introducing an |
The main motivation with this PR was actually to test on all supported Node.js major versions to avoid unintentional regressions like the one now caught in the test error. But it sounds like Node.js 16 is not supported by these packages (anymore). What is the currently supported Node.js version range for these packages? |
.nvmrc
.nvmrc
with version set tov20