Repository navigation
ci: pin Node 24 runtime to an exact patch - #1342
Merged
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
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.
Summary
Pin the seven Node 24 setup steps to 24.22.1, the security-patched runtime selected by the latest main CI run. Floating major selectors can install newer patches than the version Renovate evaluated for its release-age policy.
Release-age gate
The Actions Node 24.22.1 distribution was published on October 21 at 14:43:51 UTC. Its 14-day cutoff is November 4, 2026, at 14:43:51 UTC. Do not merge earlier without an explicit exception; this PR does not waive the policy. The pin retains the security fixes rather than reverting to an older, age-eligible patch.
Validation
Using the checksum-verified official Node 24.22.1 distribution and npm 11.19.1:
npm ci,make format, viewer and root lint, and Svelte checking passed.