-
Notifications
You must be signed in to change notification settings - Fork 16
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
feat: updated node to v20 #378
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #378 +/- ##
=======================================
Coverage 70.87% 70.87%
=======================================
Files 28 28
Lines 412 412
Branches 89 87 -2
=======================================
Hits 292 292
Misses 119 119
Partials 1 1 ☔ View full report in Codecov by Sentry. |
…ner-record into bilalqamar95/node-v20-upgrade
Pulled the branch and tried to do a bit of testing. Everything seemed to be working at this point and I think this should be safe to merge. |
@BilalQamar95 I went to approve and merge this today but realized another PR I merged recently may have caused a conflict in the package-lock file. Any chance you could fix this up and i'll approve and merge it as a fast follow? Thanks in advance! |
…ner-record into bilalqamar95/node-v20-upgrade
@justinhynes I have resolved conflicts & updated the PR |
Part of #298 |
Description
package-lock.json
with nodev20
and NPM10
..nvmrc
tov20
lockfile
version check workflow