mirror of
https://github.com/compiler-explorer/compiler-explorer.git
synced 2026-07-22 01:46:48 -04:00
6dc342aa9d
Every CI run currently emits "Node.js 20 is deprecated" runner annotations: the workflows pin action majors that target node20 and are being forced onto node24. actionlint (added in #8912) can't catch these; it doesn't know what runtime an action's implementation targets. Bump each flagged action to its latest major, all of which target node24: - actions/checkout v4 -> v7 - actions/setup-node v4 -> v7 - actions/upload-artifact v4 -> v7 - actions/download-artifact v4 -> v8 - actions/setup-python v5 -> v7 - actions/labeler v5 -> v6 - github/codeql-action v3 -> v4 (v3 is deprecated December 2026) - peter-evans/create-pull-request v6 -> v8 - cypress-io/github-action v6 -> v7 - browser-actions/setup-chrome v1 -> v2 Checked the behaviour changes against our usage: we don't use create-pull-request's renamed git-token input or removed PULL_REQUEST_NUMBER output, nor setup-python's removed pip-install input; setup-chrome v2's Chrome-for-Testing default is fine for the Cypress job. download-artifact v8 now errors on hash mismatch (a fix we want). checkout v7 blocks fork-PR checkout under pull_request_target/ workflow_run, which no workflow here does. Left alone: actions/github-script@v7 and browser-actions/setup-firefox@v1 (their moving tags already run node24 - not flagged by the runner), and wow-actions/potential-duplicates@v1 (upstream unmaintained since 2022, no node24 release exists). The self-hosted admin-node and ce fleet runners are on 2.335.1, above the 2.327.1/2.329.0 minimums these majors require. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>