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

use updating node versions in CI #286

Merged
merged 4 commits into from Dec 5, 2022
Merged

use updating node versions in CI #286

merged 4 commits into from Dec 5, 2022

Conversation

paulirish
Copy link
Member

@paulirish paulirish commented Dec 2, 2022

.....

okay it it looks happy now :)

@@ -10,20 +10,20 @@ jobs:
runs-on: ubuntu-latest
strategy:
matrix:
# awaiting support for 'latest'/'lts'. https://github.com/actions/setup-node/issues/26
node: [ '12', '14', '16', '17' ]
node: [ 'latest', 'lts/*', 'lts/-1' ]
Copy link
Member

Choose a reason for hiding this comment

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

One (small) advantage of the explicit version numbers is it matches what's in the package.json engines field. Usually they naturally get updated together (the 12 tests will fail if you update package.json but not the test matrix), but in this world these versions could keep advancing and engines could bit rot if nobody files an issue (and we don't release a breaking change but stop testing on older node versions).

One option is keeping an explicit oldest version in the matrix? Annoying if it duplicates a version, though. Maybe more important on the LH repo since it'll be testing chrome-launcher on its full version matrix.

Copy link
Member Author

Choose a reason for hiding this comment

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

true

@paulirish paulirish merged commit c753ba0 into main Dec 5, 2022
@paulirish paulirish deleted the nodevers branch December 5, 2022 20:14
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.

None yet

2 participants