Release J2K 0.11.2 - #119
Merged
Merged
Conversation
Base automatically changed from
perf/remaining-cpu-codec-optimizations
to
main
September 27, 2026 01:13
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.
Prepares all 25 published J2K crates for 0.11.2 after the codec improvements and subsampled-origin regression fix. Internal dependencies and fuzz lockfiles advance together; the dated changelog and reviewed API evidence compare against the published 0.11.1 baseline. Ordinary stable APIs remain compatible, with one additive Metal buffer-release API and five additive hidden native adapters.
Validation: CPU codec suites passed (1,631 tests; four ignored), the origin regression passed across full/reduced/region decode, all 30 release-planning tests passed, the public API/semver gate passed, and publish-mode release integrity passed. Package verification, hosted Rust quality/documentation, and exact-head quick CUDA/Metal validation passed; hosted macOS validation is running. Publication requires successful full hosted and CUDA/Metal validation on the final main candidate, followed by the existing tag-triggered publishing workflow.