Complete component-grid release evidence and freeze 0.11.1 notes - #87
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.
The J2K 0.11.1 full validation found that the new component-grid RGB planner's capability rejection was not covered. Add contract checks showing that grayscale input and explicit alpha are rejected instead of synthesizing or dropping channels, and check the unsupported-geometry diagnostic. Freeze the release notes for September 7 UTC.
Both affected native integration suites pass.
cargo xtask coverage host --base 10c34aedfc38b117bc994a14b8e394dc94675ed2passes at 100% of the 67 changed measurable host lines and the one critical-path line. Coverage thresholds are unchanged. Publication integrity also passes. Production codec behavior is unchanged. The release remains blocked until the new candidate's complete CPU/GPU gates pass.