Repository navigation
fix: pin the image to Node.js 24.22.1 security release, release 0.1.33 - #112
Merged
Merged
Conversation
Contributor
Author
|
Thanks @SpontaneousOverthrow. One thing before this merges: the
Nothing to change in the branch. Once the tag carries |
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.
Outcome
The dashboard image runs on Node.js 24.22.1, the October 21, 2026 security release (HIGH severity fixes in the 24.x line).
What changed
Dockerfile: both stages pinned from the floatingnode:24-alpinetonode:24.22.1-alpine, so a cached old24-alpinelayer cannot slip through.package.jsonandCHANGELOG.md: release 0.1.33.Accepts when
node:24.22.1-alpineis published on Docker Hub (docker-node PR feat: Node.js 22.23.4, 24.22.1, 26.12.1 nodejs/docker-node#2662 merged; image builds were still running when this PR opened)dockerjob builds both architectures green on this branchv0.1.33publishes the imageEvidence
Risk
Production deploy configuration (the published image's base). No code, dependency or lock file change.
Note: if CI runs before Docker Hub has the tag, the
dockerjob fails on a missing manifest; re-run it once the tag exists.Requested by @SpontaneousOverthrow via Slack. Owner: @SpontaneousOverthrow.