-
Notifications
You must be signed in to change notification settings - Fork 3.4k
[ci] Update 'latest' version of node to v24. NFC #24449
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: main
Are you sure you want to change the base?
Conversation
Alternatively, instead of pinning it at 24, we could call this |
The idea is that current is supposed to be LTS, which would be 22.16... that also needs updating :) |
Oh wait.. I misread your comment. Will update. |
Done. |
650f2de
to
066d677
Compare
The wasm64 tests modes already require this. Split out from #24449
Also update wasm-esm-integration tests to require v24 rather than canary.
@@ -1070,6 +1077,7 @@ jobs: | |||
EMTEST_SKIP_SCONS: "1" | |||
EMTEST_SKIP_RUST: "1" | |||
EMTEST_SKIP_NODE_CANARY: "1" | |||
EMTEST_SKIP_ESM_INTEGRATION: "1" |
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.
Where is this not skipped, after this PR?
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.
Anywhere that has node 24 or above installed
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.
We could replace this with EMTEST_SKIP_SKIP_NODE24
I suppose but the general approach so far seems to be per-feature flags.
Actually it looks like we can simplify things by landing this first: #24478 |
…en-core#24465) The wasm64 tests modes already require this. Split out from emscripten-core#24449
We can now use this for testing wasm64 and esm integration.