Repository navigation
fix: use maintained Node 24 Docker image and CI version - #5
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
node:24.15.0-bookworm-slimimages in both Docker stages with the floatingnode:24-bookworm-slimtag.node-version: 24for CI validation instead of pinning 24.15.0.A fresh source/image rebuild after merge should pick up the currently patched Node 24 image. Future security patches still require a new deployment.
Validation
24-bookworm-slimdigest matches24.22.1-bookworm-slimat the time of this PR update.pnpm checkpassed on Node 24.22.1 (typecheck, 26 tests). Workflow formatting and diff checks passed.Generated by an AI agent on behalf of Brooks Lybrand. Model: shopify/auto; reasoning: medium.