chore: Upgrade Node.js harness runtime to 24#3954
Closed
mrousavy wants to merge 1 commit into
Closed
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
mrousavy
force-pushed
the
chore/upgrade-node-24
branch
from
0b0b0fc to
2f5a152
Compare
Owner
Author
|
Superseded by #3959. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
actions/setup-nodepins from Node.js 20 to 24engines.nodefloor at>=20because the package/runtime contract does not need to become stricter for this workflow-only changeSource
Validation
source ~/.nvm/nvm.sh && nvm use 24.16.0 && node --version && npm --version && bun install --frozen-lockfileruby -e 'require "yaml"; ARGV.each { |f| YAML.load_file(f); puts "#{f}: ok" }' .github/workflows/harness-android-emulator.yml .github/workflows/harness-aws-device.yml\n-git diff --check\n\n## Notes\nHarness tests are allowed to remain red per repo-owner guidance; this PR only updates the runtime used before those harness steps run.