Skip to content

Commit af0ecf0

Browse files
Itay Inbarclaude
andcommitted
ci(pages): opt the Pages actions into Node 24
The deploy run warns that configure-pages@v5, upload-pages-artifact@v3, and deploy-pages@v4 still run on Node.js 20 — which GitHub forces to Node 24 on 2026-06-02 and removes on 2026-09-16. No newer majors move them to Node 24 yet, so set FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true at the workflow level (GitHub's documented opt-in). Silences the warning now; a no-op once Node 24 is the default. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 parent c24bf5a commit af0ecf0

1 file changed

Lines changed: 9 additions & 0 deletions

File tree

.github/workflows/pages.yml

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,15 @@ concurrency:
2020
group: pages
2121
cancel-in-progress: true
2222

23+
# The official Pages actions below (configure-pages@v5, upload-pages-artifact@v3,
24+
# deploy-pages@v4) still ship on the Node.js 20 runtime, which GitHub forces to
25+
# Node 24 on 2026-06-02 and removes on 2026-09-16. There are no newer majors that
26+
# move them to Node 24 yet, so opt in now — this silences the deprecation warning
27+
# and is a no-op once Node 24 becomes the default. Remove when the actions ship
28+
# Node-24 majors.
29+
env:
30+
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
31+
2332
jobs:
2433
deploy:
2534
runs-on: ubuntu-latest

0 commit comments

Comments
 (0)