-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node-version-file
should support absolute paths
#852
Comments
Hello @sidvishnoi. Thank you for your report. We'll take a look on it. |
Hi folks, I'm running into this issue as well, trying to use It's a pretty frustrating and unexpected behavior as far as I can tell. Any hope to see a fix to this soon? 🙌 |
@actions/setup-actions-team @HarithaVattikuti Apologies for the pings, but it looks like Dmitry hasn't been active on this project in a long time, and this issue may have slipped through the cracks. It would be awesome if someone could take a look at this and any other issues that may have been buried. |
Description:
If we pass a absolute path to
node-version-file
, for example, when using with Composite Actions, the resulting path is resolved incorrectly, due to apath.join()
call.setup-node/src/main.ts
Lines 96 to 100 in 5e21ff4
Action version:
v3
Platform:
Runner type:
Tools version:
Repro steps:
.nvmrc
, use following as input:Example broken action run: https://github.com/sidvishnoi/mediasession/actions/runs/6158104300/job/16710218833?pr=1
Expected behavior:
If it can check whether provided
node-version-file
exists as is, or perhaps usepath.resolve()
, it won't break with absolute paths.Actual behavior:
The text was updated successfully, but these errors were encountered: