engines support #94
Comments
|
Will track the work with #32. If there's anything in addition to what's in that issue, can you add a comment to that one? I would like to capture all the similar work in one place. Thanks! |
krzyk
pushed a commit
to krzyk/setup-node
that referenced
this issue
Apr 11, 2023
….5.0 update version to 1.5.0
deining
pushed a commit
to deining/setup-node
that referenced
this issue
Nov 9, 2023
Bumps [typescript](https://github.com/Microsoft/TypeScript) from 4.0.5 to 4.1.2. - [Release notes](https://github.com/Microsoft/TypeScript/releases) - [Commits](microsoft/TypeScript@v4.0.5...v4.1.2) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
It would be great if setup-node would automatically pick the correct version specified in our package.json engines property.
We're using github actions for 7 packages now and while all have an .nvmrc & specified engines still have to use the workaround provided in: #32 (comment)
Related to: #32, #26
The text was updated successfully, but these errors were encountered: