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.js to v18 #170

Merged
merged 1 commit into from
Jul 5, 2023
Merged

Upgrade Node.js to v18 #170

merged 1 commit into from
Jul 5, 2023

Conversation

victorlin
Copy link
Member

Description of proposed changes

Node.js v16 will reach end-of-life status on 2023-09-11.

Node.js v18 should also come with performance improvements during run time.

Related issue(s)

Testing

  • Checks pass

Node.js v16 will reach end-of-life status on 2023-09-11.

Node.js v18 should also come with performance improvements during run
time.
@victorlin victorlin requested a review from a team June 30, 2023 18:08
@victorlin victorlin self-assigned this Jun 30, 2023
Copy link
Member

@tsibley tsibley left a comment

Choose a reason for hiding this comment

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

This seems good to me… though I'm not totally sure how to evaluate what it could potentially break. Auspice should be just fine, and we're only using Node for Auspice, right?

@victorlin
Copy link
Member Author

Yes Auspice should be fine. "We" (the Nextstrain core team) are only using Node.js for Auspice. There's nothing stopping other users of the Docker image from using Node.js for other purposes, though the chance of that happening + breakage from this upgrade seems unlikely to me.

If we had some sort of changelog for the Docker image then this would be worth mentioning, but that's not in place.

@victorlin
Copy link
Member Author

The PR-triggered CI runs are failing due to what should be unrelated reasons, but I'll still hold off until it passes.

  • Attempts 1, 2 failed on the same action, which succeeded on attempt 3 so those were transient.
  • Attempt 3 failed because it was re-run with "failed jobs only". That option doesn't work with our CI setup because the successful built images that are pushed to GHCR get deleted upon cleanup of failed runs.

@tsibley
Copy link
Member

tsibley commented Jul 5, 2023

If we had some sort of changelog for the Docker image then this would be worth mentioning, but that's not in place.

Agreed! A changelog for our runtimes would be useful. In particular because our runtimes intentionally do not offer any compat guarantees between versions. This is for a few reasons, but the primary one is that it would be a lot of maintenance overhead (and difficult) to make those guarantees. The expectation is that if you require strict behavioral compat, you stick with a specific runtime version. We could document this better… that's part of the work I want to do on runtime documentation (nextstrain/cli#288).

That option doesn't work with our CI setup…

Oh right, I knew this but had forgotten. 🤦‍♂️

@victorlin victorlin merged commit 64fcc1f into master Jul 5, 2023
@victorlin victorlin deleted the victorlin/use-nodejs-18 branch July 5, 2023 23:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

2 participants