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(ci): update ci to test against node 14.19.1 #12264

Merged
merged 1 commit into from
Sep 29, 2022

Conversation

miketheman
Copy link
Member

@miketheman miketheman commented Sep 24, 2022

We didn't maintain parity when upgrading last time.

Instead of trying to keep two items in sync, use the engines keyword
in package.json to set the desired node version, and have the CI
action use it for setup.

I have yet to find a way to use the same value in a Dockerfile
definition, but one fewer location seems better.

Refs: https://docs.npmjs.com/cli/v8/configuring-npm/package-json#engines
Functionality to support this not yet released on actions/setup-node 🤦

Signed-off-by: Mike Fiedler miketheman@gmail.com

@miketheman miketheman requested a review from a team as a code owner September 24, 2022 21:31
@miketheman miketheman force-pushed the miketheman/upgrade-node-in-ci branch 4 times, most recently from 267374c to 6d87416 Compare September 28, 2022 15:35
We didn't maintain parity with Dockerfile* when upgrading last time.

Signed-off-by: Mike Fiedler <miketheman@gmail.com>
@ewdurbin ewdurbin merged commit b7ec571 into pypi:main Sep 29, 2022
@ewdurbin
Copy link
Member

Thanks Mike!

@miketheman miketheman deleted the miketheman/upgrade-node-in-ci branch September 29, 2022 01:47
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