Bundled actions/cache still runs on Node.js 20

[AndriyKalashnykov]

Description

When using actions/setup-go@v6.3.0 with cache: true, the workflow produces the following annotation:

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026.

While setup-go v6.3.0 itself requires Node.js >= 24 (package.json), it bundles @actions/cache which internally resolves to actions/cache@0400d5f... — still running on Node.js 20.

Expected Behavior

The bundled actions/cache dependency should be updated to v5.0.3+ which already supports Node.js 24.

Steps to Reproduce

1. Use actions/setup-go@v6.3.0 with cache: true in any workflow
2. Observe the Node.js 20 deprecation annotation referencing actions/cache@0400d5f...

Additional Context

• actions/cache v5.0.3 already requires node >= 24
• The Node.js 20 deprecation deadline is June 2, 2026

[priyagupta108]

Hello @AndriyKalashnykov 👋,
Thank you for reporting this issue. We will investigate it and get back to you as soon as we have some feedback.

[priyagupta108]

Hi @AndriyKalashnykov ,

actions/setup-go uses the @actions/cache package from @actions/toolkit for caching, and it’s currently pinned to @actions/cache@^5.0.1, which is compatible with Node.js 24.

I tried to reproduce the annotation on my side, but couldn’t get it to appear in my test runs. Here's a screenshot for your
reference.

Could you please share a link to a workflow run where the annotation appears? That will help us investigate what’s causing it. Thanks!

[priyagupta108]

Hi @AndriyKalashnykov, just following up on this. Could you please share a workflow run link where the annotation appears? That would help us investigate further. Thanks!