Chore(deps): bump cosmos/iavl v1.2.4 to v1.2.8#118
Merged
Conversation
TxCorpi0x
approved these changes
Apr 9, 2026
TxCorpi0x
left a comment
Contributor
There was a problem hiding this comment.
@TxCorpi0x reviewed 7 files and all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on masihyeganeh, miladz68, and ysv).
ysv
approved these changes
Apr 10, 2026
ysv
left a comment
Contributor
There was a problem hiding this comment.
@ysv reviewed 7 files and all commit messages.
Reviewable status:
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
3 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.
Description
Bumps github.com/cosmos/iavl from v1.2.4 to v1.2.8 (latest of the v1.2.x backport line).
Why?
Mainnet full nodes show runaway
application.dbgrowth despite aggressive pruning config. The symptom matches iavl#1063:nodeDB.deleteVersiontreatsErrVersionDoesNotExistas fatal and silently halts pruning, dangling roots accumulate, no error logged.Same bug observed by Osmosis operators (see #1065 description).
Fixes pulled in (v1.2.4 → v1.2.8)
#1065 (backport of #1063) — primary fix: continue pruning when version not found
#1067 — get-latest-version after legacy pruning fails
#983 — wait for previous batch on importer.Commit
#1142 — fast-node cache vs db commit race
#1029 — rootkey cache perf (~27% faster pruning)
Refs: v1.2.4...v1.2.8 compare · CHANGELOG@v1.2.8
Testing
Tested on mainnet node "Corium", confirmed that
iavl-v1.2.8version is backwards compatbile with existing mainnet versioniavl-1.2.4.Reviewers checklist:
Authors checklist
This change is