chore: downgrade lockfile to match orchard v0.11.0#18
Merged
Conversation
Propagates the lockfile downgrade from valargroup/voting-circuits#14 (merged) down to the iOS SDK shielded-vote branch. Pulls in the new voting-circuits + orchard revs (ecca2f0) and runs cargo update --precise across multiple passes to push transitive versions back to what orchard v0.11.0 relies on. ## Reduction - Before: 176 crates drifted from orchard v0.11.0 - After: 104 crates remain drifted 72 crates successfully downgraded. The remaining 104 are blocked by the iOS SDK's non-orchard dependency graph: - arti crates pull rand 0.9 (orchard and all Zcash crypto use rand 0.8) - zcash_primitives 0.26.1 pins prerelease RustCrypto (sha2 0.11.0-pre.4, block-buffer 0.11.0-rc.3, crypto-common 0.2.0-rc.1, bip32 0.6.0-pre.1) - tonic/reqwest/hyper dep chains pull newer futures/hashbrown/h2 - clap 4.x required by CLI tooling - tokio 1.51 required by the FFI async layer cargo build --release passes with the downgraded lockfile. Addresses Sean's P4 concern: "some of them definitely got inherited by sdk/circuits (which I also downgraded and backed out and cleaned up locally with some success)". Co-Authored-By: Claude <noreply@anthropic.com>
czarcas7ic
changed the title
greg0x
pushed a commit
that referenced
this pull request
Apr 13, 2026
chore: downgrade lockfile to match orchard v0.11.0
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.
Summary
Propagates the lockfile downgrade from valargroup/voting-circuits#14 (merged) down to the iOS SDK. Pulls in the new voting-circuits + orchard revs (
ecca2f0) and runscargo update --preciseacross multiple passes to push transitive versions back to what orchard v0.11.0 relies on.Reduction
The remaining 104 are blocked by the iOS SDK's non-orchard dependency graph:
articrates pullrand 0.9(orchard and all Zcash crypto userand 0.8)zcash_primitives 0.26.1pins prerelease RustCrypto (sha2 0.11.0-pre.4,block-buffer 0.11.0-rc.3,crypto-common 0.2.0-rc.1,bip32 0.6.0-pre.1) — upstream zcash decision, not ourstonic/reqwest/hyperdep chains pull newerfutures/hashbrown/h2clap 4.xrequired by CLI toolingtokio 1.51required by the FFI async layerContext
Addresses Sean's P4 concern (direct quote):
Test plan
cargo build --releasepasses (3m08s)c00f26dtoecca2f0(post-voting-circuits#14 main HEAD)librustvotingstill pinned to8ff4432(can be bumped once chore: downgrade lockfile to match orchard v0.11.0 zcash_voting#16 merges)