Repository navigation
Conversation
This branch has not been deployed
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.
The workspace pins blake3 to
>=1.5, <1.6because 1.6+ pullsconstant_time_eq 0.4, which needs edition 2024 / MSRV 1.85, and this workspace's MSRV is 1.83.The cap is enforced transitively on every downstream consumer, though: Cargo will not hold two semver-compatible blake3 versions, so any consumer needing blake3 ^1.8 (hologram-live needs it for iroh 1.3) cannot resolve at all.
This change keeps the workspace's own lockfile on 1.5.x (MSRV 1.83 unaffected —
cargo check -p uor-prism-crypto --lockedpasses) while relaxing the requirement so newer-toolchain consumers are not capped.