Repository navigation
feat: add minimal node image to verify tag_ranges - #2
Merged
Merged
Conversation
Adds _base/images/node, a deliberately trivial image (FROM scratch, one ARG, one LABEL - no install step) whose only purpose is to prove ContainerHive/ContainerHive#241's tag_ranges resolves a real version from Docker Hub at discovery time and threads it through as the NODEJS_VERSION build arg: tag_ranges: - tag_name: "{{.full}}" source: type: dockerhub image: library/node select: major: { last: 1 } minor: { last: 1 } patch: { last: 1 } versions: nodejs: "{{.full}}" Verified locally against a tag_ranges-capable ch build: `ch generate` resolved the live Docker Hub tag list to a single concrete tag (e.g. 26.8.1) and NODEJS_VERSION=26.8.1 came out the other end of buildconfig_resolver unchanged. Regenerated both CI pipelines to add the resulting node build/test/ manifest jobs and the version-cache steps on generate+lint (also picking up unrelated pending regen output: the ci_cancel_outdated concurrency block and action version bumps that were already sitting uncommitted before this branch). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
|
||||||||||||||
|
||||||||||||||||||
|
||||||||||||||||||||||||||
|
||||||||||||||
|
||||||||||||||||||||||
This was referenced Sep 9, 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
1 participant
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.
Verification test project for ContainerHive/ContainerHive#251 (
tag_ranges, closes ContainerHive#241).What
Adds
_base/images/node: a deliberately trivial image (FROM scratch, oneARG, oneLABEL— no install step) whose only purpose is to provetag_rangesresolves a realversion from Docker Hub at discovery time and threads it through as a build arg:
Verified locally:
ch generateresolved the live Docker Hub tag list to a singleconcrete tag and
NODEJS_VERSIONcame out the other end ofbuildconfig_resolverunchanged.
Both CI pipelines were regenerated against
ghcr.io/containerhive/containerhive:cefac90— the snapshot image published from ContainerHive#251's branch, which is where
tag_rangessupport actually lives — so this PR's own CI run doubles as the end-to-endverification.
🤖 Generated with Claude Code