actions/setup-node v4.0.4 hangs indefinitely

[peaceiris]

Description:
actions/setup-node hangs during workflow execution, causing the step to facing at timeout without progressing.

Action version:
v4.0.4

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Tools version:

Repro steps:

Expected behavior:
The action should set up Node.js successfully and allow the job to proceed to the next step.

Actual behavior:
The step hangs with no output, and the job does not proceed further.

[peaceiris]

I believe it is abnormal for this step to take more than 4 minutes. Could the cache-related incident that occurred yesterday still be ongoing?

GitHub Status - Incident with Actions

[priya-kinthali]

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

[peaceiris]

I created a repository for reproduction. When I ran it, the issue was successfully reproduced with the version v4.0.4.

https://github.com/peaceiris/repro-actions-setup-node-timeout

CI log
https://github.com/peaceiris/repro-actions-setup-node-timeout/actions/runs/15295721091/job/43024248157

[edward-simpson]

I'm seeing this happen with 4.4.0

Edit: I was looking at the wrong place for the earliest tag, the commit # is 39370e3 which looks like it's v4

[diofeher]

I'm seeing this happening on actions/setup-node@1e60f620b9541d16bece96c5465dc8ee9832be0b # v4.0.3. Could be related to what we're seeing on opentofu/vscode-opentofu#19

[priya-kinthali]

Hello @peaceiris👋,
Thank you for sharing the details related to your issue.
Since you're using setup-node@v4.0.4, please note that this version relies on an older release of @actions/cache package, which can lead to caching problems or compatibility issues. To resolve this, please upgrade to the latest version of actions/setup-node, either by specifying setup-node@v4.4.0 or by using the setup-node@v4 tag. The v4 tag will always point to the most up-to-date version, including the latest fixes and improvements for caching.

The setup-node action leverages the @actions/cache package from the actions/toolkit for its caching functionality. For more details, you can refer to the discussion here. Hope this clarifies!
@edward-simpson, @diofeher, could you please let us know if upgrading to the latest v4 resolves the issue on your end as well?
Thank you!

[peaceiris]

@priya-kinthali Thanks! I got it. I will use the latest version.

[diofeher]

It worked, thanks @priya-kinthali !

[priya-kinthali]

Thank you all for confirming!😊
Glad to hear the issue was resolved by upgrading to the latest version of setup-node. I’ll go ahead and close this issue now.
If you have any further concerns, please don’t hesitate to reach out.
Thanks again!