> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/fundamentals/announcements/deprecation-of-node-20-on-github-actions-runners.md). # Deprecation of Node 20 on GitHub Actions Runners {% hint style="info" %} **This change applies only to GitHub projects scanned using GitHub Actions** (a `codescan.yml` workflow that calls the CodeScan scanner action). If you use the native CodeScan–GitHub integration, where scans are triggered from within CodeScan with no YAML workflow file, this change does not affect you, and no action is required. {% endhint %} #### **Overview** As part of GitHub's ongoing platform maintenance, the Node 20 runtime on GitHub Actions runners is being retired and replaced by Node 24. To ensure your scans continue running without interruption, CodeScan will release an updated scanner action (`@3.0`) on **July 31, 2026**. We recommend updating your workflow ahead of GitHub's key deadline: **September 16, 2026**, when Node 20 is removed entirely. Your scan functionality remains the same—this is a runtime update only. #### Key Dates 1. **June 2, 2026:** Runners begin using Node 24 by default. Workflows on older action versions may start to fail. 2. **July 31, 2026:** Updated CodeScan scanner action release. 3. **September 16, 2026:** Node 20 is fully removed. Any workflows not yet updated will stop running. #### Actions Required Update the following action versions in your `codescan.yml` workflow: 1. `codescan-io/codescan-scanner-action` : `@2.0` → `@3.0` 2. `actions/checkout` : `@v4` → `@v6` 3. `actions/cache` : `@v4` → `@v5` 4. `github/codeql-action/upload-sarif` : `@v3` → `@v4` 5. `actions/upload-artifact` : `@v3`/`@v4` → `@v6` #### Custom (Self-Hosted) Runners If you run your GitHub Actions workflows on custom (self-hosted) runners rather than GitHub-hosted ones, an additional step is required beyond updating your action versions: 1. **Update your action versions** in `codescan.yml` (as listed in *Actions Required* above). 2. **Upgrade your runner** to a version that supports Node 24 (**v2.328.0 or later**), and confirm operating system and architecture compatibility: * Node 24 is **not compatible with macOS 13.4 or earlier** — please upgrade the operating system on affected runners. * **ARM32 is no longer supported** — these runners will stop working once Node 20 is removed. #### Runtime Configuration Options GitHub provides two environment variables to help you manage the transition on your own timeline. These are optional—updating your Action versions as described above is the recommended path. 1. **Test Node 24 ahead of time:** To opt in to Node 24 now and validate your workflow before the June 2, 2026 default switch, set `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true` as an environment variable in your workflow file or on the runner. 2. **Temporarily continue on Node 20:** Once Node 24 becomes the default, you can temporarily opt out by setting `ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true`. This is a short-term measure only; **it will stop working once Node 20 is removed on September 16, 2026**. #### Need Help? 1. Contact AutoRABIT Support (). 2. Refer to the [GitHub Changelog](https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/) for additional details. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://knowledgebase.autorabit.com/fundamentals/announcements/deprecation-of-node-20-on-github-actions-runners.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.