-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
BREAKING: drop support for Node.js v16, v21 #164
Conversation
No dependency changes detected. Learn more about Socket for GitHub ↗︎ 👍 No dependency changes detected in pull request |
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.
LGTM.
@@ -11,7 +11,7 @@ jobs: | |||
runs-on: ubuntu-20.04 | |||
strategy: | |||
matrix: | |||
node-version: [16.x, 18.x, 20.x] | |||
node-version: [18.x, 20.x] |
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.
Are we avoiding adding 22.x
here due to CI fails? https://github.com/MetaMask/eth-json-rpc-middleware/actions/runs/9993141696/job/27619854892?pr=317
Apparently that issue is fixed as of v22.5.1 nodejs/node#53935 (@cryptodev-2s), so it should be safe to add v22 if we can specify a minimum version in this field.
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.
Not per se, I also think v22 can be safely added!
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.
I guess pending GitHub runners getting up to date?
https://github.com/MetaMask/eth-json-rpc-filters/actions/runs/10013606103/job/27681585965?pr=179
Related
Blocked by
Blocking