Upgrade GitHub Actions for Node 24 compatibility#222
Open
salmanmkc wants to merge 1 commit intoaidenybai:mainfrom
Open
Upgrade GitHub Actions for Node 24 compatibility#222salmanmkc wants to merge 1 commit intoaidenybai:mainfrom
salmanmkc wants to merge 1 commit intoaidenybai:mainfrom
Conversation
Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
Contributor
|
This run croaked 😵 The workflow encountered an error before any progress could be reported. Please check the link below for details. |
Contributor
|
@salmanmkc is attempting to deploy a commit to the Million Team on Vercel. A member of the Team first needs to authorize it. |
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
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
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
actions/checkoutv4v6actions/setup-nodev4v6Context
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
always-authwas removed — if your workflow uses it, the step may failSecurity 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
v4→v6action upgrades potentially causing pipeline failures.Overview
Updates CI workflows to use
actions/checkout@v6andactions/setup-node@v6(fromv4) across lint/typecheck, build, CLI tests, and E2E runs, keeping Node pinned to20and 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
Migration
Written for commit b6e659a. Summary will update on new commits.