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: nodejs v20 #4131
chore: nodejs v20 #4131
Conversation
.github/workflows/benchmark.yml
Outdated
@@ -24,7 +24,7 @@ jobs: | |||
- name: Setup Node | |||
uses: actions/setup-node@v3 | |||
with: | |||
node-version: '18.20.1' | |||
node-version: 20 |
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.
Call me paranoid, but I tend to prefer putting exact version numbers in here. One less thing that might randomly start failing on some random day (especially with backport branches...)
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.
Yeah, I had an internal debate about this and settled on how it's probably not an issue since Node is super stable in my experience and v20 is LTE on top of that. I don't have a strong opinion on it though.
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.
Yeah I don't recall being broken by a Node minor/patch version bump, but at this point I don't trust any dependency anymore. ๐
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.
See above
Details
Update Node.js to v20.
Does this pull request introduce a breaking change?
Does this pull request introduce an observable change?
GUS work item
W-15451296