Repository navigation
chore(ci): rebuild image to pick up latest node 22.x - #33
Merged
Merged
Conversation
Piccirello
approved these changes
Oct 22, 2026
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.
Problem
The released image was built on 2026-09-01. The Dockerfile installs Node from NodeSource's floating
setup_22.xchannel, so the image only gets Node patch releases when it is rebuilt. There have been no commits tomainsince, so the image still runs an older Node 22.x.Changes
main.How did you test this code?
Not tested yet. After merge,
node --versionin the new image should printv22.23.4or later.