Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix GitHub Actions: Node.js 20 Deprecation Warning for setup-node and upload-artifact [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#24979•Fetched 2026-04-09 08:16:38
View on GitHub
Comments
1
Participants
1
Timeline
5
Reactions
0
Author
JayadityaGitJayadityaGit
Participants
JayadityaGitJayadityaGit
Timeline (top)
labeled ×2commented ×1mentioned ×1subscribed ×1
RAW_BUFFERClick to expand / collapse

Problem

GitHub Actions has deprecated Node.js 20. The following warning is shown during workflow runs:

Warning: Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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. 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/

This warning currently impacts actions/setup-node and actions/upload-artifact which are widely used across multiple workflows in .github/workflows/ including:

  • ci.yml
  • evals-nightly.yml
  • release-promote.yml
  • chained_e2e.yml
  • And many others.

Expected Behavior

We should update these actions or set the appropriate environment variable (FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true) to use Node.js 24 and clear the deprecation warnings before the deadline.

Additional Context

The current pinned hashes for actions/setup-node and actions/upload-artifact correspond to v4. Updating to v4.1 or later (or whatever versions support Node.js 24) and updating the ratcheted hashes should resolve this issue.

extent analysis

TL;DR

Update the pinned hashes for actions/setup-node and actions/upload-artifact to versions that support Node.js 24 to resolve the deprecation warnings.

Guidance

  • Check the GitHub Actions documentation and the actions' repositories for the latest versions that support Node.js 24.
  • Update the workflow files (e.g., ci.yml, evals-nightly.yml, release-promote.yml, chained_e2e.yml) to use the latest versions of actions/setup-node and actions/upload-artifact that support Node.js 24.
  • Alternatively, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in the workflow file to opt into Node.js 24 immediately.
  • Verify that the updated workflows run without deprecation warnings.

Example

steps:
  - name: Setup Node.js
    uses: actions/setup-[email protected] # or later version that supports Node.js 24

Notes

The exact version of actions/setup-node and actions/upload-artifact that supports Node.js 24 is not specified in the issue, so it's essential to check the documentation and repositories for the latest information.

Recommendation

Apply workaround: Update the pinned hashes for actions/setup-node and actions/upload-artifact to versions that support Node.js 24, as this will ensure compatibility with the upcoming default Node.js version.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#environment variable#authentication setup#request error#file not found#serialization error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING