GitHub Actions runners are deprecating Node 20 — actions still pinned to Node-20 versions emit warnings on every run and will break on these dates:
- 2026-06-02: runners force Node 24 by default (still revertible via
ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true).
- 2026-09-16: Node 20 removed from runners entirely.
Sites flagged in PR #172 CI annotations:
actions/checkout@v4 (used in ci.yml + likely mutants.yml + fuzz.yml + bench.yml + kani.yml + release-plz.yml)actions/setup-node@v4
Suggested fix: bump to the latest major (probably @v5 for both — verify on https://github.com/actions/checkout/releases + https://github.com/actions/setup-node/releases first since action majors don't align with Node-version majors).
Mechanical sweep across .github/workflows/*.yml. No behavioral change expected; CI remains gating.
Reference: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
GitHub Actions runners are deprecating Node 20 — actions still pinned to Node-20 versions emit warnings on every run and will break on these dates:
ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true).Sites flagged in PR #172 CI annotations:
actions/checkout@v4(used in ci.yml + likely mutants.yml + fuzz.yml + bench.yml + kani.yml + release-plz.yml)actions/setup-node@v4Suggested fix: bump to the latest major (probably
@v5for both — verify on https://github.com/actions/checkout/releases + https://github.com/actions/setup-node/releases first since action majors don't align with Node-version majors).Mechanical sweep across
.github/workflows/*.yml. No behavioral change expected; CI remains gating.Reference: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/