You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello @abidbmt 👋,
Thank you for reporting this issue. The issue was caused by a temporary outage on the Node.js website affecting downloads. According to the Node.js status page, the issue has now been resolved. Please try rerunning your workflows. If the problem persists, feel free to reach out to us.
Hello @abidbmt,
The issue was caused by a temporary outage on the Node.js website, which has now been resolved. I will close this issue for now. If you continue to experience any problems, please feel free to reopen this issue or create a new one.
Thank you!
Description:
Using
latest
in thenode-version
option makes the action return code 1 without any errors, not even with debug prints onAction version:
4.0.3
Platform:
Runner type:
Tools version:
N/A
Repro steps:
Use
latest
innode-version
optionExpected behavior:
Would run normally just as if you used
>=22
instead oflatest
Actual behavior:
Job fails and returns code 1 with no errors
Full workflow:
The text was updated successfully, but these errors were encountered: