Repository navigation
fix: Run Backstage on the patched Node 24.22.1 - #95
Merged
Merged
Conversation
The October 2026 Node.js security release ships 24.22.1. The backend image followed the floating Node 24 tag, so the patch reached it only on whatever rebuild happened to pull a fresh base, and nothing showed which Node a given image ran. Pin every stage to node:24.22.1-trixie-slim. The exact tag makes the running Node version visible in the Dockerfile and lets Renovate propose each later Node 24 patch as its own change.
ecv
marked this pull request as ready for review
October 21, 2026 23:43
ecv
requested review from
0xmc,
kevwilliams,
mattdjenkinson,
privateip and
scotwells
October 21, 2026 23:43
scotwells
approved these changes
Oct 21, 2026
3 tasks
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
The October 2026 Node.js security release fixes Node 24 in version 24.22.1. Our Backstage image followed a floating Node 24 tag, so it picked up the fix only by chance on a rebuild, and nobody could tell which Node a given image ran.
This change pins every build stage to Node 24.22.1 on the same Debian base. Future Node 24 patches now arrive as their own Renovate updates.
Test plan
Related to #94
Related to datum-cloud/infra#7439