Skip to content
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

chore: replace environment variables with package.json entries #287

Merged
merged 3 commits into from
Oct 17, 2024

Conversation

jbergstroem
Copy link
Member

@jbergstroem jbergstroem commented Sep 5, 2024

According to actions/node-setup, it will read manifest.engine values to decide what node version to use.
Second, the lockfile path is only relevant if it is non-default.

Refs: https://github.com/actions/setup-node/blob/main/docs/advanced-usage.md#node-version-file

@jbergstroem jbergstroem marked this pull request as draft September 5, 2024 14:24
@jbergstroem jbergstroem force-pushed the feat/engines branch 2 times, most recently from f85bc8b to 8ef351f Compare September 5, 2024 14:26
@jbergstroem
Copy link
Member Author

jbergstroem commented Sep 5, 2024

This should really work according to the code. I'm a bit baffled. Also, node 20 should be default by now..

https://github.com/actions/setup-node/blob/main/src/util.ts#L18-L31

@jbergstroem jbergstroem marked this pull request as ready for review October 17, 2024 10:29
@jbergstroem jbergstroem enabled auto-merge (squash) October 17, 2024 10:30
According to `actions/node-setup`, it will read `manifest.engine` values
to decide what node version to use. Second, the lockfile path is only
relevant if it is non-default.
@jbergstroem jbergstroem merged commit 2baae62 into main Oct 17, 2024
3 checks passed
@jbergstroem jbergstroem deleted the feat/engines branch October 17, 2024 10:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants