Skip to content

Upgrade GitHub Actions for Node 24 compatibility - #44

Open
BingqingLyu wants to merge 1 commit into
mainfrom
fork-pr-1876-upgrade-github-actions-node24
Open

Upgrade GitHub Actions for Node 24 compatibility#44
BingqingLyu wants to merge 1 commit into
mainfrom
fork-pr-1876-upgrade-github-actions-node24

Conversation

@BingqingLyu

@BingqingLyu BingqingLyu commented Apr 27, 2026

Copy link
Copy Markdown
Owner

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 08c6903 de0fac2 Release build-and-publish-image.yml, ci.yml, docs-page-action.yml, e2e.yml, gemini-automated-issue-dedup.yml, gemini-scheduled-issue-dedup.yml, gemini-scheduled-pr-triage.yml, qwen-code-pr-review.yml, release-sdk.yml, release-vscode-companion.yml, release.yml, terminal-bench.yml
actions/download-artifact 634f93c, v4 v7 Release ci.yml, release-vscode-companion.yml
actions/github-script 60a0d83 ed59741 Release check-issue-completeness.yml, gemini-automated-issue-dedup.yml, gemini-self-assign-issue.yml, qwen-automated-issue-triage.yml
actions/setup-node 49933ea 6044e13 Release ci.yml, e2e.yml, eval.yml, release-sdk.yml, release-vscode-companion.yml, release.yml, terminal-bench.yml
actions/setup-python a26af69 a309ff8 Release eval.yml
actions/stale 5bef64f b5d41d4 Release no-response.yml, stale.yml
actions/upload-artifact 6f51ac0, ea165f8, v4 v6 Release ci.yml, release-vscode-companion.yml, terminal-bench.yml

Context

Per GitHub's announcement, Node 20 is being deprecated and runners will begin using Node 24 by default starting March 4th, 2026.

Why this matters

  • Node 20 EOL: April 2026
  • Node 24 default: March 4th, 2026
  • Action: Update to latest action versions that support Node 24

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.

Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
Repository owner deleted a comment from github-actions Bot Apr 29, 2026
@BingqingLyu BingqingLyu added auto-merge-candidate auto-merge-candidate LOW risk, no cross-PR dependencies — safe to merge after quick review and removed auto-merge-candidate labels May 7, 2026
@github-actions

github-actions Bot commented Jul 8, 2026

Copy link
Copy Markdown

This pull request has had no activity for 60 days and is being marked as stale. It will be closed in another 30 days if no further activity occurs. To keep it open, push a new commit or leave a comment. Maintainers may apply pinned, status/blocked, status/on-hold, or status/ready-for-merge to exempt it from auto-close.

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

Labels

auto-merge-candidate LOW risk, no cross-PR dependencies — safe to merge after quick review status/stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants