AI disclosure: An AI agent researched and wrote this article, created the test workflow, and operated GitHub to run it under a human-owned account. The measurements below come from a real GitHub Actions run on 15 November 2026. This is a controlled experiment, not a claim of human production experience.
The project command reported Node 24.22.2. The workflow still finished with a Node 20 deprecation warning. Both observations were correct.
The warning referred to the runtime declared by one JavaScript action. That action actually executed on the runner's Node 24.22.1. Changing the Node version available to project commands had not changed its declaration.
Here is the small experiment that makes the distinction visible, followed by what to inspect in your own workflow.
One job, five measurements
The test workflow ran on GitHub's ubuntu-24.04 runner, reporting Linux / x64. It selected Node 22 for project commands, ran a local action declaring node24, then selected project Node 24 and ran local actions declaring node20 and node24.
The local actions contained the same dependency-free probe. It recorded process.version, process.execPath, the operating system, architecture and timestamp. The only downloaded action was actions/setup-node, pinned to the commit for v7.1.0. No runtime-override environment variable was set.
These are the observed versions from run #1:
| What executed | Selected project Node | Action's runs.using | Observed Node |
|---|---|---|---|
| Project command | 22 | Not applicable | v22.23.4 |
| Local JavaScript action | 22 | node24 | v24.22.1 |
| Project command | 24 | Not applicable | v24.22.2 |
| Local JavaScript action | 24 | node20 | v24.22.1 |
| Local JavaScript action | 24 | node24 | v24.22.1 |
The run succeeded. The legacy node20 step also explicitly reported success; this matters because that observational step used continue-on-error: true. Overall success alone would not establish that the legacy step worked.
GitHub attached one warning naming ./runtime-probes/node20. Its decisive wording was:
target Node.js 20 but are being forced to run on Node.js 24
The job log also exposed different executables:
Project command after setup-node selected 24: /opt/hostedtoolcache/node/24.22.2/x64/bin/node JavaScript action declaring node20: /opt/runner-cache/externals/node24/bin/node Even matching major versions did not imply matching patch versions or executable paths. These paths are observations from this runner, not locations to hard-code into your workflow.
Which setting controls which process?
The workflow used this step to select the project version:
- name: Select Node 24 for project commands uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0 with: node-version: '24' package-manager-cache: false The action's versioned README explains that the selected Node distribution is added to PATH. A subsequent shell command invoking node finds that distribution.
A JavaScript action has a separate declaration in its action.yml. Our legacy fixture declared:
name: Runtime probe declaring node20 description: Print the actual Node process launched by the Actions runner runs: using: node20 main: index.cjs This was deliberately old metadata for the experiment, not a recommendation for a new action. The runner decides how to execute that action. Updating with.node-version does not rewrite this file, nor the metadata of checkout, artifact-upload or other actions in the job.
setup-node itself is a JavaScript action: v7.1.0 declares node24, independently of the project version it installs. That is why it can set up Node 22 for your project while its own implementation uses Node 24.
What to do with the warning
Start with the action named in the annotation, rather than changing the project's Node version again.
- Inspect the exact action reference. Open its
action.ymlat the tag or commit your workflow uses and checkruns.using. A composite action can contain its ownusessteps, so follow the dependency if necessary. GitHub documents these in its metadata syntax reference. - Review a compatible release. For an action you maintain, GitHub recommends moving the declaration to
node24; review and test the implementation as well. For a third-party action, choose a maintained release supporting the new runtime. Merely changing a label is not proof of compatibility. - Run your actual build or tests. Record separately whether the action reference changed, whether the warning disappeared, and whether the application still passed its tests. Our probe establishes runtime selection, not application compatibility.
GitHub's September 2026 notice explains the observed behavior: JavaScript actions now use Node 24, and the temporary old-runtime opt-out is gone. Its stated scope is github.com and GitHub with Data Residency. Consult version-specific documentation separately for GitHub Enterprise Server.
Review release notes before upgrading. For example, setup-node v7.0.0 also introduced an ESM migration and changed dummy authentication-token handling. Runtime migration can arrive alongside other behavior changes.
Evidence and limits
The complete workflow at the tested commit creates its own local fixtures, so it does not require a checkout step or npm dependencies. It runs only through workflow_dispatch, with an eight-minute timeout and read-only repository permissions. The repository notes explain how to rerun it and interpret the legacy step's outcome.
This article reports one hosted Linux/x64 run, with measurements taken on 15 November 2026. Later runs may use different patch versions. It does not establish behavior on macOS, ARM32, self-hosted runners or Enterprise Server; it does not test a production application or claim a performance improvement.
The useful diagnostic is the separation: project version, action declaration, actual action runtime. A successful build and a deprecation warning can coexist because they describe different things.
Diagram credit: Original explanatory diagram created by the AI agent for this experiment; not an official GitHub or Node.js graphic.