Repository navigation
deps: follow JXR 0.4 on its main branch - #34
Merged
Merged
Conversation
JXR main moves to the 0.4 release line, built on J2K 0.13, so the 0.3 requirement no longer matches it and cargo latest would fail.
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.
JXR main moved to the 0.4 release line (frames-sg/jxr#26), built on J2K 0.13.1. wsi-rs still required
jxr = "0.3", which no longer matches JXR main, socargo latestin every CI job fails until this lands.Cargo.toml:jxr = { version = "0.4", git = …, branch = "main" }.Cargo.lockandfuzz/Cargo.lock: JXR main7e69e29(0.4.0) and J2K main0c6b6e4, the commit taggedv0.13.1. Only source and version lines change.Locally,
cargo xtask validatepasses: fmt, clippy, nextest (1357), the OpenSlide-oracle suite, the Metal library suite (1326), doc tests and docs.