Skip to content

fix: use maintained Node 24 Docker image and CI version - #5

Merged
brookslybrand merged 3 commits into
mainfrom
brooks/node-oct-2026-security
Oct 22, 2026
Merged

brookslybrand merged 3 commits into
mainfrom
brooks/node-oct-2026-security

Conversation

@brookslybrand

@brookslybrand brookslybrand commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Replace pinned node:24.15.0-bookworm-slim images in both Docker stages with the floating node:24-bookworm-slim tag.
  • Use node-version: 24 for CI validation instead of pinning 24.15.0.
  • Keep the existing Fly deploy command and build caching unchanged.

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

  • Official Docker Hub 24-bookworm-slim digest matches 24.22.1-bookworm-slim at the time of this PR update.
  • pnpm check passed on Node 24.22.1 (typecheck, 26 tests). Workflow formatting and diff checks passed.
  • Docker is not installed locally, so no container build was run.

Generated by an AI agent on behalf of Brooks Lybrand. Model: shopify/auto; reasoning: medium.

@brookslybrand brookslybrand changed the title fix: use patched Node.js 24.22.1 in production fix: rebuild Fly deployments on updated Node 24 images Oct 22, 2026
@brookslybrand brookslybrand changed the title fix: rebuild Fly deployments on updated Node 24 images fix: use maintained Node 24 Docker image and CI version Oct 22, 2026
@brookslybrand
brookslybrand merged commit a663e55 into main Oct 22, 2026
2 checks passed
@brookslybrand
brookslybrand deleted the brooks/node-oct-2026-security branch October 22, 2026 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant