Force GitHub to use the version of Node.js that it wants to use - #21
Merged
Conversation
Owner
|
What's happening: GitHub Actions runners currently execute JavaScript-based actions (like actions/checkout@v4, actions/setup-python@v5, coverallsapp/github-action@v2) on Node.js 20, which reaches EOL in April 2026. GitHub began warning about this deprecation in September 2025, and runners will switch to defaulting to Node 24 on June 16, 2026. Setting FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true opts a workflow into Node 24 early, to surface compatibility issues before the forced cutover. https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/ |
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
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.
It was failing a test and GitHub said to change from Node.js 20 to Node.js 24. So, I followed the instructions. Now the tests are all passing...