[QuantumExplorer]

Issue being fixed or feature implemented

Release GroveDB 6.0.1 and withdraw 6.0.0. Since the v6.0.0 tag (52ae761, 2026-09-08) develop has taken four changes that make 6.0.0 unsuitable to depend on: default backward-reference maintenance with per-operation declarations (#951, #953), the recursive-discovery fix over non-Merk descendants (#949, closes #890), and the registry grovedb-bincode resolution for Git consumers (#948). The 6.0.0 crates.io publish was also partial (grovedb and grovedb-merk were never published at 6.0.0).

What was done?

• Bumped all 16 GroveDB workspace crates and their internal version = "…" requirements from 6.0.0 to 6.0.1 (same file set as chore(release): bump GroveDB to 6.0.0 and bincode fork to 2.1.0 #945). grovedb-bincode / grovedb-bincode-derive stay at the published 2.1.0, unchanged since 6.0.0.
• README quick-start snippets pin 6.0.1 so a copy-paste never resolves 6.0.0.
• CHANGELOG: the [Unreleased] section is cut as [6.0.1] - 2026-09-13 (its bidirectional-references entries were already edited in place by feat!: maintain backward references automatically with cached old values #951/feat!: declare per operation, through DontCheck op twins, whether the displaced value may be a backward-reference participant #953 to describe the final API, so they are not separable into a 6.0.0 section). Added the entries build!: use published bincode 2.1.0 for Git consumers #948 and fix!: skip non-Merk descendants during recursive discovery #949 had not recorded, and a [6.0.0] - 2026-09-08 [YANKED] entry that says not to use 6.0.0 and lists what 6.0.1 changes relative to it. The date should be adjusted if the release is cut on another day.

How Has This Been Tested?

• cargo metadata --offline resolves the workspace; every GroveDB crate reports 6.0.1 and the bincode fork 2.1.0 (cargo metadata --no-deps | jq '.packages[] | "\(.name) \(.version)"').
• No Rust source changes; CI runs the suites.

Breaking Changes

None in this PR beyond the package version. Note that 6.0.1 as a whole carries API changes relative to 6.0.0 (#948, #949, #951, #953: propagate_backward_references → backwards_references: BackwardsReferences, the DontCheckForBackwardsReferences GroveOp twins, drop_flat_subtree's declaration argument, the removed per-layer estimator declarations, and the new subtree_discovery version slot). It is released as a patch because 6.0.0 is withdrawn rather than supported.

Release steps after merge

1. Create the GitHub release v6.0.1 targeting the merge commit (full SHA). The Release Crates workflow checks that the tag matches the grovedb crate version.
2. On release: published the workflow publishes the 6.0.1 crates in dependency order and skips versions already on crates.io. grovedb-commitment-tree and grovedb still fail at the end on the orchard git dependency, as at 6.0.0.
3. Optionally yank the eleven 6.0.0 crates on crates.io and prepend a warning to the v6.0.0 release notes.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • Git consumers now use the published grovedb-bincode 2.1.0 registry packages.

• Bug Fixes

  • Fixed recursive subtree discovery on GROVE_V4 when populated non-Merk descendants are present.

• Documentation

  • Updated usage examples to reference version 6.0.1.

• Chores

  • Released version 6.0.1 across GroveDB packages.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: d22728f5-336c-49e8-a452-dd574face0e7

📥 Commits

Reviewing files that changed from the base of the PR and between 8206add and 894fc2a.

📒 Files selected for processing (18)

• CHANGELOG.md
• README.md
• costs/Cargo.toml
• grovedb-bulk-append-tree/Cargo.toml
• grovedb-commitment-tree/Cargo.toml
• grovedb-dense-fixed-sized-merkle-tree/Cargo.toml
• grovedb-element/Cargo.toml
• grovedb-epoch-based-storage-flags/Cargo.toml
• grovedb-merkle-mountain-range/Cargo.toml
• grovedb-private-document-store/Cargo.toml
• grovedb-query/Cargo.toml
• grovedb-version/Cargo.toml
• grovedb/Cargo.toml
• grovedbg-types/Cargo.toml
• merk/Cargo.toml
• path/Cargo.toml
• storage/Cargo.toml
• visualize/Cargo.toml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The changelog documents release 6.0.1 and the withdrawn 6.0.0 release. README examples and GroveDB workspace manifests now reference version 6.0.1.

Changes

6.0.1 Release Alignment

Layer / File(s)	Summary
Release notes and usage examples CHANGELOG.md, README.md	The changelog records the 6.0.1 release, registry crate resolution, and the GROVE_V4 subtree discovery fix. README dependency examples use 6.0.1.
Workspace package and dependency versions */Cargo.toml	GroveDB package versions and internal dependency requirements change from 6.0.0 to 6.0.1. Existing paths, features, and optional settings remain unchanged.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other · Severity of issue fixed: Low

Merge Risk: ⚪ Minimal · up to 894fc

The release metadata, documentation examples, and workspace versions are aligned for 6.0.1, with no identified merge-blocking issue.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Out of Scope Changes check	⚠️ Warning	The version bumps, README dependency examples, 6.0.0 withdrawal entry, partial-publication documentation, and #948 release note do not implement issue #890. The #949 changelog entry is related to #890…	Move the release-only changes to a release-scoped pull request or link the applicable release issue. Keep this pull request limited to the #890 implementation, its automated validation, and directly related documentation.
Linked Issues check	❓ Inconclusive	Issue #890 requires storage-family-aware recursive discovery, cleanup of non-Merk namespaces without Merk decoding, indexed-axis cleanup, and automated validation of populated descendants. The whole d…	Provide reviewable head evidence for the existing or included #890 implementation and automated tests that exercise populated MMR descendants, each applicable storage family, authorized deletion, and complete indexed-axis cleanup.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the primary changes: releasing GroveDB 6.0.1 and withdrawing 6.0.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…

Full details: Linked Issues check

Explanation

Issue #890 requires storage-family-aware recursive discovery, cleanup of non-Merk namespaces without Merk decoding, indexed-axis cleanup, and automated validation of populated descendants. The whole diff changes manifests, README.md, and CHANGELOG.md only. The changelog claims the #949 fix, and the existing auxiliary code calls version-aware discovery and clears indexed namespaces, but the reviewed evidence does not establish the classification logic or the required runtime tests. Offline Cargo metadata resolution does not validate recursive deletion.

Full details: Out of Scope Changes check

Explanation

The version bumps, README dependency examples, 6.0.0 withdrawal entry, partial-publication documentation, and #948 release note do not implement issue #890. The #949 changelog entry is related to #890, but the other release changes are unrelated to the linked coding objective.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/grovedb-6-0-1-release-4e1e0e

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[QuantumExplorer]

Approved