Skip to content

release 0.9.0-beta.10: bsv-rs =0.9.0-beta.10 (the security prerelease) - #53

Merged
Calgooon merged 2 commits into
betafrom
repin/bsv-rs-0.9.0-beta.10
Nov 18, 2026
Merged

Calgooon merged 2 commits into
betafrom
repin/bsv-rs-0.9.0-beta.10

Conversation

@Calgooon

Copy link
Copy Markdown
Contributor

The pin bsv-rs =0.9.0-beta.9 moves to =0.9.0-beta.10 and the crate's version is cut to 0.9.0-beta.10, so that 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 the patched prerelease only with a tracker that pins it.

Commits

  • 63ea110 deps: pin bsv-rs =0.9.0-beta.10, the prerelease that carries GHSA-j4w5-4g84-q3f4's fix
  • 8103b8f release: 0.9.0-beta.10, the pin to bsv-rs 0.9.0-beta.10 (the security prerelease)

The pin and the lock

Cargo.lock moved by cargo update -p bsv-rs --precise 0.9.0-beta.10 alone. Two rows moved:

  • bsv-rs: version 0.9.0-beta.9 to 0.9.0-beta.10, checksum 4da4ae5e... to 7c56edf8.... Its dependency list is unchanged.
  • bsv-tracker (the crate's own row): version 0.9.0-beta.10, from the release commit.

No other row moved.

The package against the tag

  • The registry package's .cargo_vcs_info.json sha1 is 63686630b78bef17e0d25b24b326ae2311a7f855.
  • git ls-remote --tags https://github.com/Calhooon/bsv-rs 'v0.9.0-beta.10*' gives e52ee163... for refs/tags/v0.9.0-beta.10 and 63686630b78bef17e0d25b24b326ae2311a7f855 for refs/tags/v0.9.0-beta.10^{}.

The two match.

No answer moved

  • cargo test --locked -- --list on the base (cbc179c) and on the tip: 87 entries each, diff empty.
  • Every target's test result line is the same on the base and on the tip, timings aside.
  • tests/compact_golden.rs is unchanged and passes 11 of 11.
  • No source line of this crate changes. git grep -n 'bsv_rs::' -- src tests finds five lines, and they name only MerklePath and MerklePathLeaf: src/compact.rs:34, src/evidence.rs:3, src/evidence.rs:115 (a doctest), tests/common/mod.rs:2 and tests/transitions.rs:11.
  • diff -r of bsv-rs's src/ between the beta.9 and beta.10 packages: only src/kvstore/global.rs and src/kvstore/interpreter.rs differ. src/transaction/merkle_path.rs is byte for byte the same.
  • Outside src/ the package diff is the manifest, the lock, the changelog, tests/CLAUDE.md and the new tests/kvstore_global_selector_filter.rs.
  • bsv-rs's changelog for 0.9.0-beta.10 says "Breaking since beta.9. None."

The advisory and this crate

GHSA-j4w5-4g84-q3f4 is Medium (CVSS 3.1 5.3). It affects the prerelease line through 0.9.0-beta.9 and is patched in 0.9.0-beta.10.

The flaw: GlobalKVStore::query, get_by_controller and get_by_tags return the overlay resolver's answer "without re-checking the selector on the client side". The fix: query_overlay "now drops a decoded entry that does not satisfy the query's key, controller ..., protocol ... or tags ... before it is returned".

This crate does not reach those reads, for two reasons:

  • It calls no key-value store. src and tests name no kvstore, GlobalKVStore or query_overlay.
  • The kvstore module is not even compiled in its build. cargo tree -e features -i bsv-rs, with and without --features wasm, shows only bsv-rs's transaction, script, block and primitives features, plus wasm and futures-timer under this crate's wasm feature. bsv-rs's kvstore feature is off.

Hosts

A host changes nothing at this prerelease. No public item of this crate changes. cargo semver-checks --baseline-version 0.9.0-beta.9 --release-type patch reports 229 checks, 229 pass, 31 skip, "no semver update required". Without --release-type the tool reads a prerelease bump as major and skips every check.

CHANGELOG

## [Unreleased] stays above and empty. The new ## [0.9.0-beta.10] - 2026-11-18, directly above ## [0.9.0-beta.9], has an opening paragraph and two sections, ### Changed: the pin to bsv-rs 0.9.0-beta.10 and ### Security. Nothing below the new heading moves.

Proof (at the tip, 8103b8f; local, macOS, stable 1.98.1)

test list: 87 entries, identical to the base
per-target results identical to the base
cargo test --locked: 87 passed 0 failed
compact_golden: test result: ok. 11 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
   Generated /Volumes/Lanes/targets/tracker-090b10/doc/bsv_tracker/index.html
cargo fmt --all -- --check: ok
clippy:     Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.90s
vectors chain_events: test result: ok. 8 passed; 0 failed; 0 ignored; 0 measured; 6 filtered out; finished in 0.00s
vectors verdicts: test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 1 filtered out; finished in 0.00s
wasm32:     Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.93s
msrv rust_version: 1.88; check at 1.88:     Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.04s
locks: Cargo.lock: 1 bsv-rs
deny (--offline, local RustSec copy 233155b4): advisories ok, bans ok, licenses ok, sources ok
semver-checks vs 0.9.0-beta.9 (--release-type patch):  Checked [ 0.011s] 229 checks: 229 pass, 31 skip; Summary no semver update required;
   Uploading bsv-tracker v0.9.0-beta.10 (/Volumes/Lanes/worktrees/bsv-tracker-090b10)
warning: aborting upload due to dry run

cargo deny --locked check (online, after the push): advisories ok, bans ok, licenses ok, sources ok. It warns of one unmatched wrapper (secp256k1's bsv-rs wrapper in deny.toml); bsv-rs's dependency list is unchanged, so the graph and the warning are the same as on the base.

git diff origin/beta --stat:

 CHANGELOG.md | 12 ++++++++++++
 Cargo.lock   |  6 +++---
 Cargo.toml   |  4 ++--
 3 files changed, 17 insertions(+), 5 deletions(-)

Landing

The landing into beta and the tag v0.9.0-beta.10 are the captain's. This PR is not merged and no tag is pushed.

🤖 Generated with Claude Code

Calgooon and others added 2 commits November 17, 2026 21:47
…5-4g84-q3f4's fix

The requirement moves from =0.9.0-beta.9 to =0.9.0-beta.10 so that the
toolbox's and the CLI's beta lines, which pin bsv-rs exactly and hold one
bsv-rs per build, can follow onto bsv-rs's security prerelease.

Cargo.lock by `cargo update -p bsv-rs --precise 0.9.0-beta.10` alone: the
bsv-rs row's version and checksum move and no other row does. The package's
.cargo_vcs_info.json sha1 6368663 is the tag v0.9.0-beta.10's peeled commit.

No source line changes: the crate names bsv_rs::transaction::MerklePath and
MerklePathLeaf alone, and bsv-rs's src moves only in src/kvstore/global.rs
and src/kvstore/interpreter.rs, a module this crate's features (transaction,
wasm) do not compile. cargo test --locked: 87 passed, the same names and
answers as the base; compact_golden unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… prerelease)

The version moves to 0.9.0-beta.10 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: ## [Unreleased] stays above, empty; a new
## [0.9.0-beta.10] - 2026-11-18 sits directly above ## [0.9.0-beta.9],
in that entry's shape: "Changed: the pin to bsv-rs 0.9.0-beta.10" (no
source line changes and no answer moves, as the runs and the read of
bsv-rs's src diff show: only its kvstore module moves) and "Security"
(GHSA-j4w5-4g84-q3f4, the key-value store's selector reads, which this
crate neither calls nor compiles). Nothing below the new heading moves.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant