Repository navigation
chore: build with Node 24 - #319
Merged
Merged
Conversation
Node 24 is the current Active LTS release, while Node 22 has moved to maintenance. Building and checking the examples with it in CI keeps them aligned with the version most users now run.
redfish4ktc
added
the
chore
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Switch the Node version declared in
.nvmrcfrom 22 to 24. Node 24 is the current Active LTS release, while Node 22 is now in maintenance.The CI workflow reads its Node version from
.nvmrc(node-version-file), so the TypeScript projects are now built and checked with Node 24. The README already points to.nvmrc, so no documentation change is needed.