Update dependencies and update nodejs version#146
Conversation
|
Updated the workflow to test with nodejs 22 and 23. |
|
Merged main into this branch. |
demize
left a comment
There was a problem hiding this comment.
Can't really test currently, but CI passes and the changes are minimal. LGTM.
Unfortunately the Docker tests won't run since we seem to have been booted from the DSOS program, but oh well...
|
Might need to disable the merge queue temporarily to force the merge through; might as well leave it disabled while you’re at it… |
e806a99 to
81ba580
Compare
|
I don't remember what that force push was about. I might have force pushed the wrong branch. |
6d122d8 to
81ba580
Compare
|
I used the merge on Github to merge develop into this branch automatically before merging this into develop. |
|
I removed the requirement of having all tests run for NodeJS 20.x and 21.x, since I could not merge and the new Version requires 22.x! |
Checklist
npm run checkon the code and resolved any errors?npm testand all tests are passing?[Unreleased]heading?Description
This PR upgrades to node version 22.12.0 which is the latest LTS node version as of the creation of this PR.
All dependencies are also upgraded to the newest versions.
There were 2 changes to our code base, because upgrading dependencies required those changes:
uuid.v4function no longer internally uses an array, but instead usesUint8Array. This only affects tests.This PR uses the
~prefix for some dependency versions now:@eslint/jseslinteslint-plugin-jesteslint-plugin-prettierprettiertypescripttypescript-eslintThis is because minor versions of typescript or eslint often introduces new linter errors.
prettieris added to that list - not because it is expected to break on minor releases, but - becauseeslint-plugin-prettiermight break with a new minor version.Benefits
Up to date and no known security vulnerabilities.
Closes #145.
Closes #131.
Potential drawbacks
Maybe something could break.