Skip to content

Using version 20 ends up installing 18... #1173

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

Closed
2 of 5 tasks
Setitch opened this issue Dec 17, 2024 · 1 comment
Closed
2 of 5 tasks

Using version 20 ends up installing 18... #1173

Setitch opened this issue Dec 17, 2024 · 1 comment
Labels
bug Something isn't working needs triage

Comments

@Setitch
Copy link

Setitch commented Dec 17, 2024

Description:
Version 20 is specified as for installation, but version 18 is installed instead. [also funny, if version 22 is specified, version 22 is installed].

Action version:
4

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Repro steps:
Put action for installing node, and set node-version to 20, run action.

Expected behavior:
Expected behaviour is installing version 20 and using it in worker and also installing npm (at least npm) as now even that is not installed.

Actual behavior:
Run actions/setup-node@v4
with:
always-auth: false
check-latest: false
token: ***

Environment details
node: v18.19.1
npm:
yarn:

@Setitch Setitch added bug Something isn't working needs triage labels Dec 17, 2024
@Setitch Setitch closed this as completed Dec 17, 2024
@Setitch
Copy link
Author

Setitch commented Dec 17, 2024

Fixed by reloading actual runners (maybe something got cached inside them)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage
Projects
None yet
Development

No branches or pull requests

1 participant