Skip to content

Upgrade GitHub Actions for Node 24 compatibility#198

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

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

Conversation

@salmanmkc
Copy link
Contributor

@salmanmkc salmanmkc commented Mar 11, 2026

Warning

You may currently be seeing a warning like this in your workflow runs:

Node.js 20 actions are deprecated. The following actions are running on Node.js 20
and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8.
Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026.
Please check if updated versions of these actions are available that support Node.js 24.
To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment
variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you
can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true.
For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

The exact actions listed will vary per workflow.

Upgrades GitHub Actions to versions that support Node 24, since Node 20 is reaching EOL in April 2026.

Changes

Action Old Version(s) New Version Release Files
actions/checkout 08c6903 de0fac2 Release gemini-review.yml
actions/github-script 60a0d83 ed59741 Release gemini-dispatch.yml
actions/upload-artifact v6 v7 Release integration_test.yml, test.yml

Context

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

  • Node 20 EOL: April 2026
  • Node 24 becomes default: June 2nd, 2026

Breaking Changes

  • actions/upload-artifact (v6 → v7): Major version upgrade — review the release notes for breaking changes

Notes

Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA).

Worth running the workflows on a branch before merging to make sure everything still works.

@salmanmkc salmanmkc requested a review from mihirvala08 as a code owner March 11, 2026 11:13
@mihirvala08
Copy link
Collaborator

/run-integration-tests a63e85e

Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
@salmanmkc salmanmkc force-pushed the upgrade-github-actions-node24 branch from a63e85e to 5db2a7a Compare March 11, 2026 23:02
@mihirvala08
Copy link
Collaborator

/run-integration-tests 5db2a7a

@mihirvala08
Copy link
Collaborator

@salmanmkc Can you merge main branch changes to this?
There are changes pushed recently for fixing integration tests.

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.

2 participants