Repository navigation
fix: patch development container Node runtime to 24.22.1 - #76
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.
The floating Microsoft Node 24 development-container image currently runs Node v24.21.0. Replace its Node binary with the digest-pinned official Node 24.22.1 Bookworm binary, including inherited nvm copies, and assert the actual system and PATH-selected versions while building. Keep the existing Node 24 major and select the maintained Microsoft Bookworm image.
Validated: full development-container Docker build; the shared final-image pattern prints v24.22.1 from the normal PATH, /usr/local/bin/node, and an interactive shell after sourcing nvm. The unmodified upstream image was executed and prints v24.21.0. JSON parsing and diff checks pass. CI setup steps now use
check-latest: trueto resolve current security patches instead of stale hosted caches, preserving major-version labels; package consumer engine compatibility is unchanged. This patches development tooling; deployed consumers/provider runtimes need their own verified rollout. No deployments or releases were run.Node security advisory.
CI runtime verification: earlier fresh hosted jobs using floating
22/24selected cached Node 22.23.3/24.21.0. The setup steps now check the latest matching release. Verified the corrective head CI logs print actual Node v22.23.4 and v24.22.1 after latest-release resolution, with all checks passing. Green status was checked together with actual binary versions.