Repository navigation
release 0.9.0-beta.9: bsv-rs =0.9.0-beta.9 (the security prerelease), with the room made before 0.9.0 - #52
Merged
Merged
Conversation
…-jcm5-4m3m's fix The requirement moves from =0.9.0-beta.8 to =0.9.0-beta.9 so the toolbox's and the CLI's beta lines can follow onto it: they pin bsv-rs exactly and a build holds one bsv-rs, so they reach the patched prerelease only with a tracker that pins it. Cargo.lock moves by `cargo update -p bsv-rs --precise 0.9.0-beta.9` alone: one row, bsv-rs's version and checksum; its dependency list is unchanged and no other row moves. No source line changes. This crate names bsv_rs::transaction::MerklePath and MerklePathLeaf alone, and bsv-rs's src/transaction/merkle_path.rs is byte-identical between the two packages; the diff of src is beef.rs, beef/link.rs, the new beef/link_limits.rs and a CLAUDE.md. The 87 tests keep their names and their answers (the `--list` of the base and the tip compared, identical), and tests/compact_golden.rs passes unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ade before 0.9.0 The version moves to 0.9.0-beta.9 in Cargo.toml and in the crate's own row of Cargo.lock, so the toolbox's and the CLI's beta lines can follow onto bsv-rs's security prerelease through this crate. CHANGELOG.md: the text under ## [Unreleased] (the make-room change of PR 49) moves word for word under ## [0.9.0-beta.9] - 2026-11-17, and ## [Unreleased] stays above it, empty. Beside the moved text, in 0.9.0-beta.8's shape: "Changed: the pin to bsv-rs 0.9.0-beta.9" (no source line changes, no answer moves, as the runs and the read of bsv-rs's merkle_path.rs show) and "Security" (GHSA-33fm-jcm5-4m3m, its door is BEEF linking, which this crate does not reach). The make-room text's own "Hosts" is kept as it is, last. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e restored) The Security entry gave the advisory summary as its own words and left out "past the 128 MB Worker isolate" without marking the cut. Restored, so the quotation is exact. Co-Authored-By: Claude <noreply@anthropic.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
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 pin of bsv-rs moves from
=0.9.0-beta.8to=0.9.0-beta.9and the crate cuts 0.9.0-beta.9, so the toolbox's and the CLI's beta lines can follow onto bsv-rs's security prerelease: they pin bsv-rs exactly and a build holds one bsv-rs, so they reach it only with a tracker that pins it. This prerelease is the one the make-room change of PR 49 (7bbce4f, five types#[non_exhaustive], the labels,Verdict::new) rides: its## [Unreleased]text moves word for word under## [0.9.0-beta.9] - 2026-11-17, and## [Unreleased]stays above, empty.The commits
deps: pin bsv-rs =0.9.0-beta.9:Cargo.toml's requirement andCargo.lockbycargo update -p bsv-rs --precise 0.9.0-beta.9alone.release: 0.9.0-beta.9: the version inCargo.tomland the crate's own lock row; CHANGELOG.md.The lock
Two rows move, each for its own reason:
bsv-rs0.9.0-beta.8 -> 0.9.0-beta.9, checksum864decc6...->4da4ae5e...; its dependency list is unchanged (the pin).bsv-tracker0.9.0-beta.8 -> 0.9.0-beta.9 (the release).No other row moves.
The package against the tag
bsv-rs-0.9.0-beta.9/.cargo_vcs_info.jsonin the registry:"sha1": "a6c8676b0ea655cbc53878c46cc6f8a003fd8519"git ls-remote --tags https://github.com/Calhooon/bsv-rs 'v0.9.0-beta.9*':a6c8676b0ea655cbc53878c46cc6f8a003fd8519 refs/tags/v0.9.0-beta.9^{}They match.
No answer moved
git grep -n 'bsv_rs::' -- src tests: five lines in four files (src/compact.rs:34,src/evidence.rs:3,src/evidence.rs:115(a doctest),tests/common/mod.rs:2,tests/transitions.rs:11), each namingbsv_rs::transaction::MerklePathand/orMerklePathLeaf, nothing else.diff -rqof bsv-rs'ssrcbetween the two registry packages:src/transaction/beef.rs,src/transaction/beef/link.rs, the newsrc/transaction/beef/link_limits.rsandsrc/transaction/CLAUDE.md, nothing else.src/transaction/merkle_path.rsis byte for byte the same (cmp). The only mentions ofMerklePathin the diff are the linker reading the size of aMerklePathLeaffor its new heap charge.cargo test --locked -- --list, base (7bbce4f) against tip, with each test's target: 87 and 87,diffempty. Each passes at both (87 passed, 0 failed);tests/compact_golden.rs(PR 49's golden) untouched, 11 passed.git diff origin/beta --stattouchesCHANGELOG.md,Cargo.lockandCargo.tomlalone.The advisory, and whether this crate reaches its door
GHSA-33fm-jcm5-4m3m (High, CVSS 3.1 7.5), read with
gh api repos/Calhooon/bsv-rs/security-advisories/GHSA-33fm-jcm5-4m3m: the prerelease range it names runs through 0.9.0-beta.8, patched in 0.9.0-beta.9. In its words, cut: "the #749 link bound (GHSA-gvmh-f5gf-5vjj) meters a BEEF's serialized wire bytes but not the heap each cloned stub re-materializes - the proof a stub carries and the struct backings of its inputs and outputs - so an untrusted BEEF within the lookup resolver's size bound can force a memory-exhaustion denial of service; the fix keeps that wire budget and adds a second, heap budget beside it". The door is linking a BEEF:Transaction::from_beef(the advisory), andBeef::find_transaction_for_signing(bsv-rs's changelog).This crate does not reach that door. Through bsv-rs it builds a merkle path, reduces it to a root and reads its height; it links no BEEF:
git grep -n -iE 'bsv_rs|beef|from_beef|find_transaction' -- src tests, less the fiveMerklePathlines above, is empty. The one default of 0.9.0-beta.9 that refuses earlier (BeefLinkLimits::max_link_heap_bytes) is on that door. bsv-rs's changelog states no breaking change since 0.9.0-beta.8.What a host changes at this prerelease
The make-room change, as its Hosts section says (kept word for word):
HostAction,Reask,HintStatusorVerdictErrorgains a wildcard arm that keeps and surfaces what the host does not name (a re-ask byReask::label, an error as the fault it is), never an arm that maps toHintStatus::Unknownor drops the value.Verdictbuilt by literal becomesVerdict::new(status)with its other fields assigned after it.HintStatus({"status":"mined","height":900}) and reads it back by it, never by a hand map, and surfaces a status the reader refuses.The pin itself asks nothing of a host of this crate.
The proof, at the tip fa607cc
CARGO_BUILD_JOBS=2, a private CARGO_TARGET_DIR, cargo 1.98.1 on aarch64-apple-darwin.
The semver break is PR 49's five marks, as its changelog text states; nothing comes from the pin. The machete, secrets and actionlint jobs are CI's alone (their tools are not installed here).
Landing
The landing into
betaand the tagv0.9.0-beta.9are the captain's; this PR merges nothing and tags nothing.🤖 Generated with Claude Code