Skip to content

Bump actions off Node.js 20#23

Open
santicomp2014 wants to merge 1 commit intomainfrom
bump-actions-node24
Open

Bump actions off Node.js 20#23
santicomp2014 wants to merge 1 commit intomainfrom
bump-actions-node24

Conversation

@santicomp2014
Copy link
Copy Markdown

Summary

  • Bump the three actions flagged by GitHub's Node.js 20 deprecation warning:
    • actions/checkout v3/v4 → v5 (Node 24)
    • actions/cache v4 → v5 (Node 24)
    • actions/setup-python v4 → v6 (Node 24)
  • Applies to .github/workflows/ci.yml and .github/workflows/notify.yml.

Why

Node.js 20 actions are deprecated. … Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026.

Got the warning on the Notify / Notify job. Bumping ahead of the forced migration.

Not included (intentionally)

  • actions/upload-artifact@v4 / actions/download-artifact@v4 — still current on v4, no deprecation warning.
  • slackapi/slack-github-action@v1.27.0 — not flagged by the warning; v2+ changed the payload input format, so a bump would need payload-API migration + testing. Separate change.

Test plan

  • CI runs pass on this PR (Format / Lint / Typecheck / Tests / Coverage / Functests).
  • Watch one scheduled Notify run post-merge — no Node 20 deprecation warning, run completes successfully and pings the snitch.

🤖 Generated with Claude Code

GitHub is deprecating Node.js 20 actions (forced to Node 24 on
June 2, 2026; removed Sept 16, 2026). Bump the three flagged actions:

- actions/checkout: v3/v4 -> v5 (Node 24)
- actions/cache: v4 -> v5 (Node 24)
- actions/setup-python: v4 -> v6 (Node 24)

Leaves actions/upload-artifact@v4, actions/download-artifact@v4, and
slackapi/slack-github-action@v1.27.0 alone: the artifact actions are
still current on v4, and the Slack action would need a separate
payload-API migration (v2+ breaking change).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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