Update our build workflows to use NodeJS 22 #1285
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
xxyy2024
pushed a commit
to xxyy2024/waveterm_aipy
that referenced
this pull request
Jun 24, 2025
NodeJS 20 is almost EOL so I'm updating our workflows to use NodeJS 22. This does not change anything about our app, which will still use NodeJS 20 until Electron shifts away from it. NodeJS 22 is fully backwards-compatible with NodeJS 20 so there's no issue from a testing standpoint.
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.
NodeJS 20 is almost EOL so I'm updating our workflows to use NodeJS 22. This does not change anything about our app, which will still use NodeJS 20 until Electron shifts away from it. NodeJS 22 is fully backwards-compatible with NodeJS 20 so there's no issue from a testing standpoint.