Skip to content

feat!: Support Node 18+#2011

Merged
danielbankhead merged 9 commits intomasterfrom
prepare-node-18
Oct 4, 2024
Merged

feat!: Support Node 18+#2011
danielbankhead merged 9 commits intomasterfrom
prepare-node-18

Conversation

@danielbankhead
Copy link
Copy Markdown
Contributor

@danielbankhead danielbankhead commented Sep 18, 2024

Adding support for Node 18+. Dropping older versions of Node.

@danielbankhead danielbankhead requested a review from a team September 18, 2024 17:50
@danielbankhead danielbankhead requested review from a team September 18, 2024 17:50
SET PATH=%PATH%;/cygdrive/c/Program Files/nodejs/npm

call nvm use v14.17.3
call nvm use 18
Copy link
Copy Markdown
Contributor

@sofisl sofisl Sep 20, 2024

Choose a reason for hiding this comment

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

should it be 18.20?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This should install and use the latest version of Node 18

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think it's better to specify given we had that before, is there a reason you think it shouldn't be specified?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This would ensure the version tested has all of the latest bug fixes and features.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yes but then we could potentially be installing on other versions which would make our testing unpredictable. Note our previous versions, which have all specified an exact version: #378

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I see we have a pattern from previous iterations - however it doesn't necessarily mean it was best practice (even that linked PR suggests the same - the patch was a required manual update that we shouldn't have to do each time).

The stability for the oldest supported LTS is far less-likely to receive a bug or breaking change than a newer LTS, while taking advantage of any provided security patches. See the following:

In short, we'd be preferring the problem of slight risk of a broken release vs getting pinged for manual security patching. I'd rather deal with the slight risk of a broken release as it would block releases across the ecosystem (all open source Node projects), which wouldn't make it a pressing matter for just us.

@sofisl
Copy link
Copy Markdown
Contributor

sofisl commented Sep 20, 2024

Please use this as a model if you have any other questions! https://github.com/googleapis/synthtool/pull/1825/files

@sofisl
Copy link
Copy Markdown
Contributor

sofisl commented Sep 23, 2024

We'll want to follow up with a PR to update the Docker image dependencies once these are updated: https://github.com/googleapis/synthtool/blob/master/docker/owlbot/nodejs_mono_repo/Dockerfile#L55C1-L56C79

SET PATH=%PATH%;/cygdrive/c/Program Files/nodejs/npm

call nvm use v14.17.3
call nvm use 18
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think it's better to specify given we had that before, is there a reason you think it shouldn't be specified?

@sofisl sofisl self-requested a review October 3, 2024 23:13
@danielbankhead danielbankhead merged commit c19dd80 into master Oct 4, 2024
@danielbankhead danielbankhead deleted the prepare-node-18 branch October 4, 2024 00:08
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