Repository navigation
chore(docker): run api and web on Node 26.12.1 - #64
Merged
Merged
Conversation
Pins the runtime and build stages to the October 2026 security release instead of the floating node:22-slim tag. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
What
Dockerfile.apiandDockerfile.web:node:22-slim→node:26.12.1-slim(build + runner stages).Why
Node's October 21 security release (Brotli RCE CVE-2026-111497 plus 9 more) is fixed in 26.12.1. Pinning the exact tag makes Coolify pull the patched image instead of reusing a cached floating
22-slimlayer.Tested
/200,/games/cyberpunk-2077200, game cards render, api up with 0 restarts.🤖 Generated with Claude Code