chore(ci): bump Pages actions to Node 24 majors#171
Merged
Conversation
- actions/configure-pages: v5 → v6 - actions/upload-pages-artifact: v3 → v5 - actions/deploy-pages: v4 → v5 Silences the Node 20 deprecation warnings surfaced on every deploy-website run. All three new majors run on Node 24 (per their release notes) and keep the same input/output contract used here.
2 tasks
montfort
added a commit
that referenced
this pull request
May 19, 2026
Distill the operational knowledge accumulated across PRs #169–#171 into a new top-level §Website section in CLAUDE.md so future sessions don't have to rediscover it. Sections added: - Layout of `website/` and what each subdir is for. - npm scripts table (start/build/sync:docs/migrate:blog/clear/typecheck/ write-translations). - i18n: how locales are wired (locales array, code.json, blog translations, docs mirror via sync:docs, theme overrides). - Deploy pipeline (`deploy-website.yml` jobs + permissions, repo-side Pages config with `build_type=workflow` / `cname` / `https_enforced`). - Custom domain workflow (CNAME + url + API cname must all change together). - Build gotchas: slow-tail, no-parallel builds, avoid pipe-to-tail, `exclude` semantics, Pages source migration trap. - Verification commands for deploys. Internal docs only (`CLAUDE.md` is not shipped to adopters). Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Silences the Node 20 deprecation warnings on every
Deploy Websiterun by bumping the three Pages actions to their Node 24 majors:actions/configure-pagesv5v6actions/upload-pages-artifactv3v5actions/deploy-pagesv4v5All three new majors run on Node 24 per their release notes (
actions/configure-pagesv6 changelog: "upgrade to node 24";actions/deploy-pagesv5 changelog: "Update Node.js version to 24.x";actions/upload-pages-artifactv5 bundles upload-artifact v7). Input/output contracts used here (pathon upload, no inputs on configure/deploy) are unchanged across these majors.Context: after #169 migrated to the official Pages pipeline, runs started emitting:
GitHub will force Node 24 on June 2, 2026 and remove Node 20 from runners on September 16, 2026, so this is preemptive cleanup.
Test plan
main, confirm the auto-triggeredDeploy Websiterun (path filter matches.github/workflows/deploy-website.yml) succeeds.curl -sI https://straymark.dev/still returnsHTTP/2 200.