Problem
.github/workflows/nextjs.yml:90 pins actions/upload-pages-artifact@v4. That composite action internally pins actions/upload-artifact@v4.6.2, which is on the node20 internal runtime. The 2026-05-13 post-merge deploy run for #173 surfaced this in the annotation log:
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02
GitHub Actions hard-deprecates the Node 20 internal runtime on 2026-06-02 — after that date, the transitive call inside upload-pages-artifact@v4 will fail to start.
End state
actions/upload-pages-artifact@v4 → @v5 in .github/workflows/nextjs.yml:90.- The next merge-to-main deploy run completes green with no
Node.js 20 annotation lines.
Bump target verified
actions/upload-pages-artifact@v5.0.0 is a composite action (no internal Node runtime of its own) that internally pins actions/upload-artifact@v7.0.0 (node24).- v5.0.0 changelog: two changes — internal artifact-action bump, plus an additive
include-hidden-files input. The action's existing output contract (artifact_id, artifact_url) is unchanged.
- The website consumes only
upload-pages-artifact's outputs (it calls deploy-pages next, which pulls the artifact by name), so the upload-artifact@v4 → @v7 internal jump doesn't reach the workflow surface.
Constraints
- Single one-line bump. No other workflow changes.
- Don't touch static site contents.
Acceptance criteria
Related
Closes the website's Node 24 migration (third and final straggler). Earlier follow-ups: #173 / #174 (deploy-pages + configure-pages, merged 2026-05-13). Discovered in the #174 post-merge deploy annotation log.
Deadline
2026-06-02 (GitHub Actions Node 20 runtime hard-deprecation).
Problem
.github/workflows/nextjs.yml:90pinsactions/upload-pages-artifact@v4. That composite action internally pinsactions/upload-artifact@v4.6.2, which is on thenode20internal runtime. The 2026-05-13 post-merge deploy run for #173 surfaced this in the annotation log:GitHub Actions hard-deprecates the Node 20 internal runtime on 2026-06-02 — after that date, the transitive call inside
upload-pages-artifact@v4will fail to start.End state
actions/upload-pages-artifact@v4→@v5in.github/workflows/nextjs.yml:90.Node.js 20annotation lines.Bump target verified
actions/upload-pages-artifact@v5.0.0is a composite action (no internal Node runtime of its own) that internally pinsactions/upload-artifact@v7.0.0(node24).include-hidden-filesinput. The action's existing output contract (artifact_id,artifact_url) is unchanged.upload-pages-artifact's outputs (it callsdeploy-pagesnext, which pulls the artifact by name), so theupload-artifact@v4 → @v7internal jump doesn't reach the workflow surface.Constraints
Acceptance criteria
nextjs.yml:90readsuses: actions/upload-pages-artifact@v5.nextjs.ymldeploy run completes green.Node.js 20deprecation warning lines in the run log.Related
Closes the website's Node 24 migration (third and final straggler). Earlier follow-ups: #173 / #174 (deploy-pages + configure-pages, merged 2026-05-13). Discovered in the #174 post-merge deploy annotation log.
Deadline
2026-06-02 (GitHub Actions Node 20 runtime hard-deprecation).