Repository navigation
chore(release): bump GroveDB to 6.1.0 - #1022
Merged
Merged
Conversation
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>
|
Waiting for bot review — coderabbitai not yet · thepastaclaw not yet. Wait for the missing reviews, or a writer can post |
Contributor
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing (18)
✨ Finishing Touches
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. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 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
🚀 New features to boost your workflow:
|
3 of 9 tasks
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.
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_V4fixes 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?
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-bincodeandgrovedb-bincode-derivestay at the published 2.1.0.6.1.0.[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 --offlinereports 6.1.0 for every GroveDB crate and 2.1.0 for the bincode fork.Breaking Changes
This PR changes only the package version. The release itself carries API changes relative to 6.0.1, recorded in the CHANGELOG:
impl PendingOperations).GROVE_V4version slots, so code that builds those version structs by hand must set them; fix(batch)!: commit same-batch sum-item references and replacements to the bytes stored (GROVE_V4) #1021 also changes some Merk put function signatures.GroveOpgains a variant, so an exhaustive match on it must handle the new one.Release steps after merge
v6.1.0targeting the merge commit (full SHA). The Release Crates workflow checks that the tag matches thegrovedbcrate version.release: publishedthe workflow publishes the 6.1.0 crates in dependency order and skips versions already on crates.io.grovedb-commitment-tree(and sogrovedb) still depends onorchardby 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:
For repository code-owners and collaborators only
🤖 Generated with Claude Code
PR Hygiene ·
7f6f491/skip-botsproceeds without the ones not yet reported/self-reviewedWhen every merge requirement is met, the
PR Hygienecheck passes. Reviewer limits do not block merging; other required GitHub checks and protections still apply.