chore: use the latest cometbft-db in v0.38.x (backport #4297)#4422
Merged
mergify[bot] merged 1 commit intov0.38.x-experimentalfrom Nov 4, 2024
Merged
Conversation
Co-authored-by: Anton Kaliaev <anton.kalyaev@gmail.com> (cherry picked from commit 28a308f)
melekes
approved these changes
Nov 4, 2024
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
2 participants
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.
The goal of this PR is to allow users to use the latest set of db backends with the 38 release series. Alternatively, we could add something to the cometbft-db v0.13.0 release notes that let users of cometbft-db know that it and following versions are incompatible with v0.38.x.