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 to nodejs 18.18.2 #101

Merged
merged 3 commits into from
Nov 17, 2023
Merged

upgrade to nodejs 18.18.2 #101

merged 3 commits into from
Nov 17, 2023

Conversation

shannonwells
Copy link
Collaborator

@shannonwells shannonwells commented Nov 17, 2023

Problem

Upgrade to nodejs 18+. Closes #83

Solution

Used last patch version of nodejs 18

Change summary:

  • changed .tool-versions,
  • changed package.json and
  • ran npm install to update package-lock.json
  • updated all Git workflows
  • updated @types/node
  • updated README

Steps to Verify:

CI should pass

Copy link
Member

@wilwade wilwade left a comment

Choose a reason for hiding this comment

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

Found a few more places to update, but everything is working

  • Ran locally
  • Built
  • Ran thrift

package.json Show resolved Hide resolved
@@ -1 +1 @@
nodejs 16.15.1
nodejs 18.18.2
Copy link
Member

Choose a reason for hiding this comment

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

Found a few more places to update:

  • Readme was already out of date, but should be updated: _parquet.js requires node.js >= 14.16.0_
  • The GitHub Action workflows still use v16. 18+ might require updating the version of the actions/checkout, actions/setup-node, and actions/cache actions, although I think the new version of setup-node might not require the actions/cache anymore.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I created another upgrade issue with these items in a checklist.

Copy link
Member

Choose a reason for hiding this comment

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

That sounds good. More of an Actions upgrade issue.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

looks like CI is ok with the actions versions for now. maybe add it to the next upgrade issue?

@shannonwells shannonwells requested a review from wilwade November 17, 2023 21:56
Copy link
Member

@wilwade wilwade left a comment

Choose a reason for hiding this comment

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

🚢

@@ -1 +1 @@
nodejs 16.15.1
nodejs 18.18.2
Copy link
Member

Choose a reason for hiding this comment

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

That sounds good. More of an Actions upgrade issue.

Copy link
Member

@wilwade wilwade left a comment

Choose a reason for hiding this comment

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

Approving to make sure to capture all the changes

@shannonwells shannonwells merged commit bda4e3f into main Nov 17, 2023
1 check passed
@shannonwells shannonwells deleted the upgrade-to-nodejs-18 branch November 17, 2023 22:09
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.

Upgrade to Node 18+
2 participants