Skip to content

Force GitHub to use the version of Node.js that it wants to use - #21

Merged
jakehadar merged 1 commit into
jakehadar:masterfrom
kjcole:fixes
Aug 16, 2026
Merged

Force GitHub to use the version of Node.js that it wants to use#21
jakehadar merged 1 commit into
jakehadar:masterfrom
kjcole:fixes

Conversation

@kjcole

@kjcole kjcole commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

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...

@jakehadar

Copy link
Copy Markdown
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/

@jakehadar
jakehadar merged commit e6d738b into jakehadar:master Aug 16, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants