Repository navigation
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.
Images can grow while remaining 100% layer-efficient, and the current compare verdict does not enforce image-size limits. This adds opt-in size budgets shared by CI and comparison, plus a clearer comparison report that leads with totals, failed checks, and the largest changes.
--max-image-sizeand--max-growth; CI growth checks require--baseline OLD.Validation:
go test -race -count=1 -p 2 ./...passed with no exclusions in the official Go 1.27.3 container; additional race checks passed for final CLI/viewer changes.layerx buildwith analysis export.Podman was not installed locally, so live Podman coverage remains for CI; existing mocked engine/resolver tests passed. macOS and Windows arm64 were cross-compiled, not runtime-tested.