ci: Move GitHub Actions off Node 20 action runtimes (#14930)
### Description
Node 20 reached end of life on 2026-04-30, and GitHub is deprecating it
as a JavaScript action runtime. 64 action references across 12 files
under `.github/` still pinned releases whose `action.yml` declares
`using: node20`, or `node16` for `slack-github-action@v1.23.0`. This PR
repins each one to a release that declares `node24`, checked at the
exact SHA, reusing SHAs the repo already pins where one exists.
| Action | From | To | Uses |
| --- | --- | --- | --- |
| `actions/checkout` | v4 (`34e1148`) | v6.0.2 | 30 |
| `actions/download-artifact` | v4 (`d3f86a1`) | v8.0.1 | 12 |
| `actions/upload-artifact` | v4 (`ea165f8`) | v7.0.1 | 8 |
| `actions/cache`, `cache/restore`, `cache/save` | v4 (`0057852`) |
v5.0.5 | 6 |
| `pnpm/action-setup` | v4 (`f40ffcd`) | v5.0.0 | 2 |
| `oven-sh/setup-bun` | v2.0.1 | v2 (`0c5077e`, already used in repo) |
2 |
| `actions/setup-node` | v4 (`49933ea`) | v6.4.0 | 2 |
| `slackapi/slack-github-action` | v2.0.0, v1.23.0 | v3.0.5 | 2 |
The two `setup-node` steps in `turborepo-test.yml` that pinned an
explicit Node version (`"18.20.2"`, `"20"`) now use `"24.22.2"`. The
`[22, 24, 26]` matrices and the `node-version-file: package.json`
default in `.github/actions/setup-node` are unchanged.
**Breaking-change review** (from each release's notes, checked against
how these workflows use the action):
- **slack-github-action v1.23.0 → v3:** the release workflow's "Notify
Slack on failure" step passed the webhook through the
`SLACK_WEBHOOK_URL` env var, which v2 removed. It now uses `webhook` +
`webhook-type: incoming-webhook` with the same secret, matching how
`docs-alias-failure-notification.yml` already sends to that webhook. The
payload is unchanged. Under v1, a webhook with no `SLACK_WEBHOOK_TYPE`
was sent as a Workflow Builder trigger, so this step's `text`/`blocks`
payload is now delivered as an incoming-webhook message, the same way
the other workflow already sends to it.
- **checkout v6:** persisted credentials move to a file under
`$RUNNER_TEMP`. 29 of the 30 checkouts already set `persist-credentials:
false`. The `turborepo-library-release.yml` build jobs that run inside
`node:20-alpine` and `amazon/aws-lambda-nodejs:20` containers still
work: the runner mounts `$RUNNER_TEMP` into job containers, and it ships
a `node24_alpine` external for JavaScript actions in Alpine containers.
- **download-artifact v5–v8:** single downloads by `artifact-ids` now
extract directly into `path`, and digest mismatches now fail the job.
Every download here is by `name` or `pattern`.
- **setup-node v5/v6:** automatic caching now applies only to npm
projects. This repo uses pnpm, and neither step sets `cache:`.
- **cache v5**, **upload-artifact v5–v7** and **pnpm/action-setup v5**
list only the Node 24 runtime (or ESM packaging) as breaking. The inputs
passed here are unchanged.
**Out of scope:**
- `arduino/setup-protoc` (`.github/actions/setup-protoc`) still runs on
Node 20, and its latest release (v3.0.0) has no Node 24 version. It
needs a replacement, such as installing `protoc` from the GitHub release
directly.
- The `node:20-alpine` / `aws-lambda-nodejs:20` container images used to
build the library are separate from the action runtime.
### Testing Instructions
- Fetched `action.yml` at every new SHA: all declare `node24`.
- No old SHAs remain under `.github/`.
- actionlint 1.7.7 on the changed workflows: no findings before or
after.
- `oxfmt --check` (0.63.0, with the repo's `.oxfmtrc.jsonc`) passes on
all 12 changed files, as the pre-push `lint-staged` hook would require.
- Not run: the workflows themselves. This PR's own CI covers the test
workflows. Watch the release-only jobs on their next runs: the library
build containers in `turborepo-library-release.yml`, and the Slack
failure notification in `turborepo-release.yml`.
Co-authored-by: roboeve[bot] <311457182+roboeve[bot]@users.noreply.github.com>