-
Notifications
You must be signed in to change notification settings - Fork 549
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
test against Node.js nightlies #2932
Comments
Maybe run against nightlies scheduled every day and if it errors it should create an issue in this repo. Maybe also something we can motivate @mweberxyz ? |
Maybe it can be still done on every merge to |
Yeah this kind of thing is right up my alley I'll take a look @Uzlopak |
Current PR went with @Uzlopak suggestion to simply run on a schedule, and avoid @metcoder95 concerns of issue fatigue, it will not create new issues if one is already open. |
* chore(.github/workflows): factor out test running * chore: add nightly tests Closes #2932
I think we should set up our CI to run against Node.js nightlies, we would have caught the regression
The text was updated successfully, but these errors were encountered: