Repository navigation
chore: upgrade Node to 24.22.2 and npm to 11.19.1 - #18
Merged
Merged
Conversation
Update CI and release runners while retaining Node 22.18 compatibility coverage. Approve the pinned Lefthook installer and align the lockfile with the existing 0.2.0 package version.
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
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.
Update the current CI matrix entry, Sonar job, and release runner to Node 24.22.2, and declare npm 11.19.1 in packageManager. Correct the release comment to name that Node release’s bundled npm version. Preserve the Node >=22.18.0 engine floor and lower CI matrix entry.
Record the version-specific Lefthook install-script approval. Synchronize the lockfile’s stale 0.1.2 metadata with the package’s existing 0.2.0 version; this does not bump the package or change dependency versions.
Validation in separate temporary checkouts:
No package was published; trusted publishing remains in the existing release workflow.