0.5.x: repin librustzcash to published crates.io releases (CI)#7
Merged
Conversation
…leases The ironwood wallet crates were published to crates.io on 2026-07-12 (zcash_client_backend 0.24.0-rc.1, zcash_client_sqlite 0.22.0-rc.1, pczt 0.8.0-rc.1, zip321 0.9.0-rc.1), alongside the leaf crates as finals (zcash_primitives/zcash_proofs 0.29.0, orchard 0.15.0, zcash_protocol 0.10.0, zcash_keys 0.15.0, zcash_address 0.13.0, zcash_transparent 0.9.0). This is the repin the branch was waiting on: - Drop the [patch.crates-io] git pin of the whole librustzcash workspace (dw/ironwood-scan-model rev 1105d8203) and the shardtree/incrementalmerkletree git pins; published shardtree 0.7.0 / incrementalmerkletree 0.8.2 carry the checkpoint-retention APIs and the clear_flags panic fix the pins existed for. Only the vendored i18n-embed-fl patch remains. - Adapt to API drift between the old rev and the RC: create_proposed_transactions no longer takes a target-expiry argument; create_pczt_from_proposal and BuildConfig::Standard gain a trailing orchard_pool_bundle_type (DEFAULT, matching zecd's padded-bundle change strategy). - The RC now builds Ironwood PCZTs (librustzcash#2543 landed), so ironwood_forces_fused is a conservative choice rather than an upstream constraint; keep the gate (the fused path is the one the ironwood regtest validates) and note the follow-up. Builds clean; offline suite green (267 lib tests), fmt and clippy clean. Co-authored-by: AI <noreply+norm@overpay.com>
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.
Draft for CI. Ports the internal ironwood repin onto the public 0.5.x line: the librustzcash set moves off the git-pin (
dw/ironwood-scan-modelrev1105d8203) to the crates.io releases published 2026-07-12.Changes
zcash_client_backend 0.24.0-rc.1,zcash_client_sqlite 0.22.0-rc.1,pczt 0.8.0-rc.1,zip321 0.9.0-rc.1); leaf crates as finals (zcash_primitives/zcash_proofs 0.29.0,orchard 0.15.0,zcash_protocol 0.10.0,zcash_keys 0.15.0,zcash_address 0.13.0,zcash_transparent 0.9.0);shardtree 0.7.0/incrementalmerkletree 0.8.2. All[patch.crates-io]git pins dropped — only the vendoredi18n-embed-flremains. No git pins, no fork.create_proposed_transactionsdrops the target-expiry arg;create_pczt_from_proposal+BuildConfig::Standardgainorchard_pool_bundle_type: DEFAULT.ironwood_forces_fusednote updated — the published RC now builds Ironwood PCZTs (librustzcash#2543 landed), so the gate is conservative, not mandatory.Coherent Ironwood resolution (no duplicate sibling versions). Local:
cargo buildclean,cargo test --lib267 passed / 0 failed, fmt + clippy clean.Confirming CI + Regtest E2E + Docker before deciding on a
v0.5.0-rc3release.