-
Notifications
You must be signed in to change notification settings - Fork 71
chore: Bump node 16 (20) -> 22 #1065
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
base: master
Are you sure you want to change the base?
Conversation
The Linea SDK is a painful dependency in that it depends on better-sqlite3, and that seems to have build issues when migrating to node 22. The Linea SDK is only required here for a single script that's never actually been needed in production. To simplify things, we can migrate it to the relayer repository where we already have to deal with the Linea SDK dependencies.
16 is long EoL but we were in practice using 20 in CI.
if command -v node >/dev/null 2>&1; then | ||
if node --version 2>/dev/null | grep -q "v${{ inputs.node_version }}"; then |
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.
This pre-existing check would resolve true if the installed version of node was different to what was specified via inputs.node_version
. Harden it a bit by verifying that the actual installed version of node reports something that gives a strong hint at being the right version. This should be compatible with specifying additional constraints on the version - i.e. minor and patch levels.
I wonder if there's a cleaner way to do this - i.e. I'd suspect setup-node
has some built-in version checker, but since action was only recently by @Reinis-FRP I'm assuming there was some blocker there.
The base branch was changed.
16 is long EoL but we were in practice using 20 in CI.