Skip to content

chore(release): bump GroveDB to 6.1.0 - #1022

Merged
QuantumExplorer merged 1 commit into
developfrom
chore/release-6.1.0
Oct 13, 2026
Merged

QuantumExplorer merged 1 commit into
developfrom
chore/release-6.1.0

Conversation

@QuantumExplorer

@QuantumExplorer QuantumExplorer commented Oct 13, 2026 •

Copy link
Copy Markdown
Member

Basic explanation

What this does: It releases GroveDB 6.1.0. Every workspace crate moves from 6.0.1 to 6.1.0, and so does each internal version requirement between them. The README snippets now pin 6.1.0, and the CHANGELOG's [Unreleased] section becomes [6.1.0] - 2026-10-13.

Value: Dash Platform can depend on a tagged release that carries everything merged since 6.0.1: the GROVE_V4 fixes its protocol version 14 relies on (#1003, #1010, #1018-#1021), element moves (#1015), and the panic and proof hardening (#974, #975, #988, #990, #1006, #1011, #1012, #1016, #1017).

Risks: Low for this PR, which changes only versions, README pins and a CHANGELOG heading. The release as a whole contains breaking API changes (see "Breaking Changes").

Issue being fixed or feature implemented

develop has moved well past 6.0.1 (2026-09-13). Platform currently pins a develop revision; a release gives it a version to depend on.

What was done?

  • Bumped all 16 GroveDB workspace crates and their internal version = "…" requirements from 6.0.1 to 6.1.0, the same file set as chore(release): bump GroveDB to 6.0.1 and withdraw 6.0.0 #960. grovedb-bincode and grovedb-bincode-derive stay at the published 2.1.0.
  • The README quick-start snippets pin 6.1.0.
  • CHANGELOG: the [Unreleased] entries are cut as [6.1.0] - 2026-10-13, under a new empty [Unreleased] heading. Adjust the date if the release is cut on another day.

How Has This Been Tested?

  • cargo metadata --no-deps --offline reports 6.1.0 for every GroveDB crate and 2.1.0 for the bincode fork.
  • No Rust source changes; CI runs the suites.

Breaking Changes

This PR changes only the package version. The release itself carries API changes relative to 6.0.1, recorded in the CHANGELOG:

Release steps after merge

  1. Create the GitHub release v6.1.0 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.1.0 crates in dependency order and skips versions already on crates.io. grovedb-commitment-tree (and so grovedb) still depends on orchard by git tag (dashified-0.14.1), so those two fail to publish at the end, as they did at 6.0.0 and 6.0.1.

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

PR Hygiene · 7f6f491

  • Bots — coderabbitai not yet · thepastaclaw not yet — /skip-bots proceeds without the ones not yet reported
  • Self-review — post /self-reviewed
  • Build running
  • Approvals — you own every area touched; none needed

When every merge requirement is met, the PR Hygiene check passes. Reviewer limits do not block merging; other required GitHub checks and protections still apply.

Bump the 16 GroveDB workspace crates and their internal version
requirements from 6.0.1 to 6.1.0, pin 6.1.0 in the README snippets, and
cut the CHANGELOG's Unreleased section as 6.1.0 (2026-10-13). The
grovedb-bincode fork stays at 2.1.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Waiting for bot review — coderabbitai not yet · thepastaclaw not yet. Wait for the missing reviews, or a writer can post /skip-bots to proceed without them; blocking findings still need addressing.
Full checklist in the description.

@github-actions github-actions Bot added the waiting-bots Waiting for the review bots to report on this head label Oct 13, 2026
@coderabbitai

coderabbitai Bot commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

Review in Change Stack →

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 2759f428-806d-4cc8-adb5-479072a886aa
📥 Commits

Reviewing files that changed from the base of the PR and between 7ea60ee and 7f6f491.

📒 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
 ____________________________________________________________________
< Love the minimalism. Unfortunately the feature was also minimized. >
 --------------------------------------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       /   づ
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

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

@QuantumExplorer
QuantumExplorer merged commit fc7028d into develop Oct 13, 2026
4 of 6 checks passed
@QuantumExplorer
QuantumExplorer deleted the chore/release-6.1.0 branch October 13, 2026 13:40
@codecov

codecov Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.21%. Comparing base (5cb0962) to head (7f6f491).
⚠️ Report is 2 commits behind head on develop.

Additional details and impacted files
@@            Coverage Diff            @@
##           develop    #1022    +/-   ##
=========================================
  Coverage    93.20%   93.21%            
=========================================
  Files          352      356     +4     
  Lines       108428   108953   +525     
=========================================
+ Hits        101062   101556   +494     
- Misses        7366     7397    +31     
Components Coverage Δ
grovedb-core 91.59% <92.15%> (+0.01%) ⬆️
merk 94.18% <94.46%> (-0.03%) ⬇️
storage 91.68% <ø> (ø)
commitment-tree 95.62% <ø> (ø)
mmr 95.43% <ø> (ø)
bulk-append-tree 93.72% <ø> (ø)
element 97.39% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

waiting-bots Waiting for the review bots to report on this head

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant