Repository navigation
ci: resolve patched Node instead of stale runner caches - #508
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.
Fresh GitHub jobs with floating supported Node majors can select vulnerable preinstalled tool-cache binaries: an observed runner used Node 22.23.3 and 24.21.0. Resolve the latest matching release during setup so the October 2026 patched runtimes (22.23.4/24.22.1/26.12.1) are used. Preserve existing major-version matrix labels and published consumer compatibility.
Validation: edited workflow/composite YAML parses and diff checks pass. Current actions/node-versions manifest contains 22.23.4, 24.22.1, and 26.12.1. New-head CI logs verify actual patched Node 24.22.1. All CI checks pass. No production deployments, migrations, settings changes, or manual release/sync workflows were triggered.
Node security advisory.