Skip to content

Upgrade GitHub Actions for Node 24 compatibility#222

Open
salmanmkc wants to merge 1 commit intoaidenybai:mainfrom
salmanmkc:upgrade-github-actions-node24
Open

Upgrade GitHub Actions for Node 24 compatibility#222
salmanmkc wants to merge 1 commit intoaidenybai:mainfrom
salmanmkc:upgrade-github-actions-node24

Conversation

@salmanmkc
Copy link

@salmanmkc salmanmkc commented Mar 7, 2026

Summary

Upgrade GitHub Actions to their latest versions to ensure compatibility with Node 24, as Node 20 will reach end-of-life in April 2026.

Changes

Action Old Version(s) New Version Release Files
actions/checkout v4 v6 Release code-quality.yml, publish-any-commit.yml, test-build.yml, test-cli.yml, test-e2e.yml
actions/setup-node v4 v6 Release code-quality.yml, publish-any-commit.yml, test-build.yml, test-cli.yml, test-e2e.yml

Context

Per GitHub's announcement, Node 20 is being deprecated and runners will begin using Node 24 by default starting June 2nd, 2026.

Why this matters

  • Node 20 EOL: April 2026
  • Node 24 default: June 2nd, 2026
  • Action: Update to latest action versions that support Node 24

⚠️ Breaking Changes

  • actions/checkout (v4 → v6): Major version upgrade — review the release notes for breaking changes
  • actions/setup-node (v4 → v6): Major version upgrade — review the release notes for breaking changes
    • ⚠️ Input always-auth was removed — if your workflow uses it, the step may fail

Security Note

Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references.

Testing

These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.


Note

Low Risk
Workflow-only changes; primary risk is CI behavior differences from the v4v6 action upgrades potentially causing pipeline failures.

Overview
Updates CI workflows to use actions/checkout@v6 and actions/setup-node@v6 (from v4) across lint/typecheck, build, CLI tests, and E2E runs, keeping Node pinned to 20 and existing pnpm caching.

No application/runtime code changes; this is a GitHub Actions dependency bump aimed at runner Node 24 compatibility.

Written by Cursor Bugbot for commit b6e659a. This will update automatically on new commits. Configure here.


Summary by cubic

Upgrade GitHub Actions to Node 24–compatible versions (checkout v6, setup-node v6) to prepare for Node 20 EOL and upcoming runner defaults. No application code or project Node version changes.

  • Dependencies

    • actions/checkout: v4 → v6
    • actions/setup-node: v4 → v6
    • Action refs remain pinned to release SHAs
  • Migration

    • If any workflow used setup-node’s removed input always-auth, update it
    • Run CI on this branch to verify workflows
    • Builds still run on Node 20; update project Node separately when ready

Written for commit b6e659a. Summary will update on new commits.

Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
@pullfrog
Copy link
Contributor

pullfrog bot commented Mar 7, 2026

This run croaked 😵

The workflow encountered an error before any progress could be reported. Please check the link below for details.

Pullfrog  | Rerun failed job ➔View workflow run | Triggered by Pullfrogpullfrog.com𝕏

@vercel
Copy link
Contributor

vercel bot commented Mar 7, 2026

@salmanmkc is attempting to deploy a commit to the Million Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 5 files

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