Repository navigation
Validate manifest references and upstream build arguments - #487
Merged
Merged
Conversation
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.
A package currently passes SPEC-M05 if one service matches the declared upstream version, even when another service uses a different value. Explicit manifest service references and unsupported global-env names can also survive build-time checks and fail or silently do nothing at installation.
Check every matching build argument, accept digest suffixes only with a complete SHA-256 hash, and identify the conflicting compose fragment. Add SPEC-M10 for resolved service references and SPEC-M11 for short names from the shared runtime catalogue. Findings follow the existing warn/error/off rollout and retain source/variant attribution.
Document manifest inheritance and version semantics, move historical repository counts into a dated baseline, and derive the flexible Compose type from the shared definition so current shared types compile correctly.
Related: #367. Coordinate rollout with Shared schema/runtime; publish the shared schema/type updates first. Companion documentation: Public docs and Tropibot guide.
Validation:
globalEnvs: { all: true }form.