Update Dependencies (November 2025) #1600
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cmoesel
force-pushed
the
update-deps-nov2025
branch
from
e24873e to
11a9e16
Compare
Bump node to 22, but keep eslint and tsc targets at 2018 for compatibility
- Prefer Node 24 but keep compatibility for 18 - Update CI to run Node 24 across OSes, but run Node 18-22 on Ubuntu
…he symlink behind
Using 50% of available cores seems to run faster and will hopefully mitigate some issues running in CI.
cmoesel
force-pushed
the
update-deps-nov2025
branch
from
11a9e16 to
6c279e7
Compare
jduteau
approved these changes
Dec 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description: This PR updates all dependencies that can be reasonably updated. See DEPENDENCY-NOTES.md for exceptions. As part of this PR, I've also bumped our preferred Node version to v22, but we still maintain support for Node 18 at the moment.
I attempted to bump our preferred Node version to 24, but GitHub Actions were failing for the combination of Node 24 and macos (other operating systems were fine).
I've also turned off coverage for CI runs, fixed a deprecated uses of
fs.existsSyncand switched some sync operations to async in tests because Node 24 wasn't properly deleting files.Testing Instructions: Tests should pass and SUSHI should continue to function as normal.
Related Issue: N/A