ci(pages): bump Pages actions off deprecated Node 20 - #962
Merged
Merged
Conversation
configure-pages v5, upload-pages-artifact v4, upload-artifact v4, download-artifact v4, and deploy-pages v4 each run on (or bundle) a Node 20 runtime that GitHub is deprecating on runners. Pin them to the current Node 24 releases; inputs used here are unchanged. checkout is already Node 24, and mlugg/setup-zig v2.2.1 is the latest upstream and still Node 20 (no fix available).
drawmeanelephant
had a problem deploying
to
github-pages
September 12, 2026 15:41 — with
GitHub Actions
Failure
drawmeanelephant
marked this pull request as ready for review
September 12, 2026 15:42
This was referenced Sep 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agent Completion Report
ci/pages-actions-node24ci/pages-actions-node24(main checkout)04fda61emain.github/workflows/github-pages.ymldocs/changelog.d/962-pages-actions-node24.mdmainwas fast-forwarded toorigin/mainbefore branching, and no unrelated dirty state existed.actions/configure-pagesv5 → v6.0.0,actions/upload-pages-artifactv4 → v5.0.0,actions/upload-artifactv4 → v7.0.1,actions/download-artifactv4 → v8.0.1, andactions/deploy-pagesv4 → v5.0.1, all Node 24 releases. Inputs used by the workflow are unchanged across majors.actions/checkout(already Node 24 / v6) andmlugg/setup-zig(latest upstream v2.2.1, still Node 20) untouched.mlugg/setup-zigv2.2.1 is the latest upstream release and still declares Node 20; no fix is available. The runner forces it onto Node 24 and it succeeds (a warning remains).github-pagesenvironment only permits deployments frommain(confirmed via the environment's deployment branch policy).deploy-pagesv5.0.1 runs onmainafter merge. Thedownload-artifactv8.0.1 path is behind the optionalaudit_deploymentdispatch input and was not exercised.gh api repos/drawmeanelephant/boris/pages(diagnosed the original 404)gh api -X POST repos/drawmeanelephant/boris/pages -f build_type=workflow(enabled Pages)zig build testgh workflow run github-pages.yml --ref ci/pages-actions-node24gh run watch 34702825037zig build test: passci/pages-actions-node24): pass — configure-pages v6, upload-pages-artifact v5, upload-artifact v7 all succeededmlugg/setup-zigremains (upstream limitation)mainonly)github-pagesandboris-github-pages-evidence-34702825037, retained by GitHub, not committed.)GitHub Pagesrun onmaincompletes build and deploy green with only themlugg/setup-zigNode 20 warning remaining.