Prepare JXR 0.1.2 patch release - #2
Draft
jcwal1516 wants to merge 1 commit into
Draft
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.
Prepare patch versions for the merged shared reconstruction plans and MPSGraph lifetime-owner changes. Update exact internal dependency requirements and generated root/fuzz lockfiles; document the seven-package publication order. The unchanged math crate stays at 0.1.0.
This draft depends on publication of J2K 0.11.0. Before merging, replace the graph-support Git pin with its published 0.11.0 registry dependency, refresh the lockfile, and validate the final dependency graph and hardware paths.
Validation so far: corpus preparation tests, formatting, all-target/all-feature Clippy, workspace tests, no-default-feature facade tests, warnings-denied docs, and fuzz formatting/Clippy passed. The CPU T.834/T.835 comparison passed all 517 in-scope cases, with 179 declared out-of-scope cases and no failures. These checks still use the existing immutable graph-support Git pin.