chore: update rocksdb to version 0.24.0#383
Conversation
WalkthroughUpdates the RocksDB dependency in storage/Cargo.toml from version 0.23.0 to 0.24.0; the optional flag remains unchanged. No code files are modified. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
✨ Finishing Touches🧪 Generate unit tests
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 |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
storage/Cargo.toml (1)
21-21: Optional: consider jumping to a newer minor (e.g., 0.28.x) to avoid follow-up bumps.0.28.0 adds features (e.g., blob cache) and tracks RocksDB 9.4.0; if compatible, upgrading now could reduce churn. (docs.rs)
If you want to do it here, the diff is trivial:
- rocksdb = { version = "0.24.0", optional = true } + rocksdb = { version = "0.28.0", optional = true }
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
storage/Cargo.toml(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
- GitHub Check: Compilation errors
- GitHub Check: Linting
- GitHub Check: Code Coverage
- GitHub Check: Tests
🔇 Additional comments (1)
storage/Cargo.toml (1)
21-21: Unable to auto-validate RocksDB bump
Validation script failed due to missing/proc; please manually run in your local/CI environment:cargo update -p rocksdb cargo build -p grovedb-storage --features rocksdb_storage cargo test -p grovedb-storage --features rocksdb_storageto confirm that upgrading rocksdb = "0.24.0" in
storage/Cargo.tomlintroduces no regressions.
Issue being fixed or feature implemented
Update the rocksdb dependency to the latest version.
What was done?
Updated the rocksdb version in the Cargo.toml file from 0.23.0 to 0.24.0.
How Has This Been Tested?
No specific tests were mentioned, but the update should be validated through existing unit tests.
Breaking Changes
None
Checklist
For repository code-owners and collaborators only
Summary by CodeRabbit