Skip to content

chore: update GitHub Actions to Node.js 24-compatible versions#94

Open
eranchetz wants to merge 1 commit into
masterfrom
chore/node24-ci-actions
Open

chore: update GitHub Actions to Node.js 24-compatible versions#94
eranchetz wants to merge 1 commit into
masterfrom
chore/node24-ci-actions

Conversation

@eranchetz

Copy link
Copy Markdown
Contributor

Summary

  • Bump actions/checkout v4 → v5 (node24 runtime)
  • Bump actions/setup-node v4 → v5 (node24 runtime)
  • Bump aws-actions/configure-aws-credentials v4 → v5 (node24 runtime)
  • Bump actions/github-script v7 → v8 (node24 runtime)
  • Update node-version: '20''22' (Node 22 LTS) in all 3 workflows

Why

GitHub Actions is deprecating Node.js 20 for action runtimes:

  • June 2, 2026: Actions forced to Node.js 24 by default
  • September 16, 2026: Node.js 20 removed from runners entirely

All 4 workflows were emitting deprecation warnings. This brings all actions and the app runtime forward before the deadline.

Files changed

  • .github/workflows/ci.yml
  • .github/workflows/fetch-pricing.yml
  • .github/workflows/preview.yml
  • .github/workflows/preview-cleanup.yml

Test plan

  • No @v4 / @v7 / node-version: '20' references remain in .github/workflows/
  • CI passes on this PR with the updated action versions

🤖 Generated with Claude Code

Bump action versions to avoid Node.js 20 deprecation warnings:
- actions/checkout v4 → v5
- actions/setup-node v4 → v5
- aws-actions/configure-aws-credentials v4 → v5
- actions/github-script v7 → v8

Also update app node-version from '20' to '22' (current LTS).

Node.js 20 actions are deprecated and will stop working by default
on June 2, 2026 and be removed September 16, 2026.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

🔗 Preview: https://gcpinstances.doit.com/previews/pr-94/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant