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

ci: use .nvmrc for setup-node versions #24355

Merged
merged 2 commits into from
Feb 26, 2023
Merged

Conversation

nschonni
Copy link
Contributor

Description

Since the .nvmrc file was added, makes sense to use it as the base for the CI operations. Not sure if there is any difference in the cache-key calculations when a major version changes, but that's pretty infrequent

Motivation

Additional details

Related issues and pull requests

@nschonni nschonni requested a review from a team as a code owner February 11, 2023 19:28
Copy link
Contributor

@caugner caugner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FWIW node-version-file is documented here.

It also supports package.json, which might be preferable (so that it tests with the lowest version we support), but given our >=18.0.0 range, I'm not sure what version it would choose (18.0.0, latest 18.x.x or latest).

tl;dr These changes make sense, and avoid us having to touch the workflows when bumping Node.js.

Copy link
Contributor

@caugner caugner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea to run all workflows on .nvmrc change. 👍

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.

3 participants