Skip to content

v0.0.1-rc6 - #4

Merged
emersonian merged 6 commits into
mainfrom
be/rc6
Aug 20, 2026
Merged

v0.0.1-rc6#4
emersonian merged 6 commits into
mainfrom
be/rc6

Conversation

@emersonian

Copy link
Copy Markdown
Contributor

Cuts v0.0.1-rc6 on top of rc5.

What's in it

  • eada4512 ci: fold the regtest tiers back into one Ironwood stack. regtest.yml returns as the single live tier, carrying the Ironwood stack, the image matrix and the weekly zfnd/zebra:latest canary; regtest-ironwood.yml is deleted and its PR/push triggers move over. Pinned zebra stays on the released zfnd/zebra:6.0.0.
  • 08c619a3 deps: take the librustzcash line to its stable releases. zcash_primitives 0.30, zcash_keys 0.16, zcash_transparent 0.10, pczt 0.9, zip321 0.9 and the final wallet crates 0.24 / 0.22, so nothing in the graph is a pre-release. send.rs passes the new lock_inputs and expiry_height arguments as None. deny.toml drops the RUSTSEC-2026-0009 ignore now that time is unpinned, and keeps an empty git allow-list. The lockfile refresh also clears the yanked spin 0.9.8 and h2 RUSTSEC-2026-0258.
  • 672964ba version bump to v0.0.1-rc6.
  • c407ffbf website download notes to rc6.

Verified locally

cargo fmt --check, cargo clippy --workspace --all-targets -D warnings, cargo test --workspace (407 tests), cargo deny check, cargo +1.88 check --workspace --all-targets.

This PR's CI adds the folded regtest tier, running in this repo for the first time since the fold.

🤖 Generated with Claude Code

- regtest.yml returns as the single live tier, carrying the Ironwood
  stack, the image matrix and the weekly zfnd/zebra:latest canary
- regtest-ironwood.yml is deleted; its PR and push triggers move over
- the pinned zebra stays on the released zfnd/zebra:6.0.0
- zcash_primitives 0.30, zcash_keys 0.16, zcash_transparent 0.10,
  pczt 0.9, zip321 0.9 and the final wallet crates 0.24 / 0.22, so
  nothing in the graph is a pre-release any more
- send.rs passes the new lock_inputs and expiry_height arguments as
  None: spends already serialize on the per-database lock, and the
  builder-derived expiry is what we want
- deny.toml drops the RUSTSEC-2026-0009 ignore (time is unpinned now)
  and keeps an empty git allow-list
- the lockfile refresh also clears the yanked spin 0.9.8 and h2
  RUSTSEC-2026-0258
The Send modal's live address check labeled a unified address with an
Orchard receiver as "orchard", but every Orchard receiver is an Ironwood
receiver (they share the pool), and the restore flow already shows
"ironwood/orchard". Update describe_recipient's pool label to match, and
cover the unified/Orchard case in its unit test.
The RecipientInfo doc and the new test comment said the two "share the
pool". They share the Orchard *receiver*, which is what makes one
receiver serve both and is the actual reason the label is
"ironwood/orchard". The value pool is distinct: a V6 Ironwood output is
stored under pool code 4, legacy V5 Orchard under 3.
@emersonian
emersonian force-pushed the be/rc6 branch 2 times, most recently from 3ee3ac0 to a0d2936 Compare August 20, 2026 18:54
@emersonian
emersonian merged commit a0d2936 into main Aug 20, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant