-
-
Notifications
You must be signed in to change notification settings - Fork 289
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: unpin nodejs version from 22.4 #6982
base: unstable
Are you sure you want to change the base?
Conversation
This reverts commit f20484b.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## unstable #6982 +/- ##
=========================================
Coverage 49.21% 49.21%
=========================================
Files 598 598
Lines 39803 39803
Branches 2102 2104 +2
=========================================
+ Hits 19588 19589 +1
+ Misses 20175 20174 -1
Partials 40 40 |
Performance Report✔️ no performance regression detected Full benchmark results
|
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.
moving to draft as it seems we have some consensus to wait until 22 becomes active LTS |
@wemeetagain Previously we didn't had precedence to only use LTS versions, rather latest version. Even current codebase is still locked upto This PR was reverting an earlier PR because 22.5 introduced a regression, but 22.5.1 fixed it. Don't see any reason to keep restricting upto 22.4. |
I personally don't have confidence in nodejs release process for Having to debug strange node issue is not fun..and we have better things to do |
Yes, I think our experience the other day, where we had to pin the version, changed my mind a little bit. It seems that the nodejs folks treat the new version with more leeway to be actually unstable and breaking before it becomes "current". Once it becomes "current", their standards for something breaking become much higher. I tend to agree with Nico that we don't really care to have our daily progress possibly stopped again by a breaking version, and we can mitigate that by pinning a specific version until it becomes "current" LTS. |
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.
Nodejs 22 is in LTS now https://nodejs.org/en/blog/release/v22.11.0
Motivation
Use the latest stable node release.
Description
Node version 22.5.1 fixes the regressions.
Steps to test or reproduce
Run all tests.