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

Upgrade Node 16 to Node 20 #300

Merged
merged 5 commits into from
Sep 26, 2023
Merged

Upgrade Node 16 to Node 20 #300

merged 5 commits into from
Sep 26, 2023

Conversation

ThomasVitale
Copy link
Contributor

@ThomasVitale ThomasVitale commented Sep 24, 2023

  • Upgrade the action to use Node 20 instead of Node 16.
  • Migrate from @zeit/ncc to @vercel/ncc package because the former has been out of maintenance for 3 years and a transition to the latter is recommended. Change done here because @zeit/ncc doesn't provide support for Node 20.

Fixes gh-299

Fixes gh-299

Signed-off-by: Thomas Vitale <[email protected]>
The @zeit/ncc library is no longer maintained
and doesn't support Node 20.
Migrating to @vercel/ncc is recommended.

Fixes gh-299

Signed-off-by: Thomas Vitale <[email protected]>
Re-generate package-lock file after migrating
from @zeit/ncc to @vercel/ncc

Signed-off-by: Thomas Vitale <[email protected]>
Signed-off-by: Thomas Vitale <[email protected]>
@jbrunton
Copy link
Contributor

Thanks for the PR, @ThomasVitale!

I see the build is failing. I have a hunch this is unrelated and I'll check this now.

I also note that for Enterprise users with self-hosted runners, Node 20 support was only added in August (https://github.com/actions/runner/releases/tag/v2.308.0) so I suspect this may be a breaking change for some. I think when we merge this the next build should be called v2. No action required in this PR, but just a reminder to myself (and an FYI to others).

@jbrunton
Copy link
Contributor

jbrunton commented Sep 25, 2023

@ThomasVitale : Could you do me a favor to fix the build? Either merge, cherry-pick or copy and paste the changes from #301 onto your branch?

This PR needs that fix to pass, but my PR also needs (some of) the dependency upgrades in your PR to pass. Between them they should do the job.

Signed-off-by: Thomas Vitale <[email protected]>
@ThomasVitale
Copy link
Contributor Author

@jbrunton thanks for the review. Since my branch is in a fork, I couldn't cherry-pick your commit fixing the tests, so I copied the fix. I hope that's ok.

I agree about bumping the major version for the new release since it could be a breaking change.

@jbrunton
Copy link
Contributor

@ThomasVitale : thank you, that all looks good. I'll merge this and create a new version.

@jbrunton jbrunton merged commit a173dc9 into carvel-dev:develop Sep 26, 2023
10 checks passed
@jbrunton jbrunton mentioned this pull request Sep 26, 2023
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.

GH is deprecating Node.js 16 actions. Upgrade to Node 20 needed
2 participants