ci: opt workflows into Node 24 action runtime#25
Merged
Conversation
- Set FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 on release and perf workflows
- Removes GitHub Node 20 action runtime deprecation warning ahead of the June 2026 default flip
Tests: ruby -e 'require "yaml"; Dir[".github/workflows/*.yml"].each { |f| YAML.load_file(f) }'
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.
What
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24for release and perf workflows that use JavaScript actions.Why
How
envflag in the affected workflow YAML files.Testing
ruby -e 'require "yaml"; Dir[".github/workflows/*.yml"].each { |f| YAML.load_file(f) }'\n\n## Performance Impact\n- None expected; this only changes the runtime used by GitHub-hosted JavaScript actions.\n\n## Risk / Notes\n- Low. If an action is not Node 24 compatible, CI should reveal it before merge.