Summary
The v0.2.0 release run flagged the GitHub Actions Node 20 deprecation:
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4.
Non-blocking (the runner force-runs them on Node 24, so publish still succeeded), but worth clearing before the forced-migration deadline. See https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Where
Both workflows pin the v4 majors, which target the Node 20 runtime:
.github/workflows/ci.yml:15-16 — actions/checkout@v4, actions/setup-node@v4.github/workflows/release.yml:20-21 — actions/checkout@v4, actions/setup-node@v4
Fix
Bump both to the latest majors that run on Node 24 (actions/checkout@v5, actions/setup-node@v5) in both workflows. Then confirm CI (Validate) still passes; the release workflow only re-runs on the next published release, so double-check the OIDC id-token: write publish path is unaffected (it should be — the version bump doesn't touch auth).
Low priority / housekeeping.
Summary
The
v0.2.0release run flagged the GitHub Actions Node 20 deprecation:Non-blocking (the runner force-runs them on Node 24, so publish still succeeded), but worth clearing before the forced-migration deadline. See https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Where
Both workflows pin the v4 majors, which target the Node 20 runtime:
.github/workflows/ci.yml:15-16—actions/checkout@v4,actions/setup-node@v4.github/workflows/release.yml:20-21—actions/checkout@v4,actions/setup-node@v4Fix
Bump both to the latest majors that run on Node 24 (
actions/checkout@v5,actions/setup-node@v5) in both workflows. Then confirm CI (Validate) still passes; the release workflow only re-runs on the next published release, so double-check the OIDCid-token: writepublish path is unaffected (it should be — the version bump doesn't touch auth).Low priority / housekeeping.