chore(store/v2): bump iavl

[tac0turtle]

Description

bump store v2 to iavl v1.1.0

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• updated the relevant documentation or specification, including comments for documenting Go code
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

• Chores
  • Updated the github.com/cosmos/iavl library to version v1.1.0 for improved stability and performance.

[coderabbitai]

Walkthrough

Walkthrough

This update involves upgrading the github.com/cosmos/iavl dependency in the store module from version v1.0.0-beta.1.0.20240125174944-11ba4961dae9 to v1.1.0. This change suggests an improvement or addition of features, optimizations, or bug fixes in the iavl package which could impact how the store module interacts with the IAVL (Immutable AVL Tree) data structure used in Cosmos SDK applications.

Changes

Files	Change Summary
store/go.mod	Updated github.com/cosmos/iavl to v1.1.0
store/go.sum	Updated hashes for github.com/cosmos/iavl to v1.1.0

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yml

Commits

Files that changed from the base of the PR and between 0a98bfb and e4ac665.

Files selected for processing (2)

• store/go.mod (1 hunks)
• store/go.sum (1 hunks)

Additional comments: 2

store/go.mod (1)

• 13-13: The update of the github.com/cosmos/iavl dependency from v1.0.0-beta.1.0.20240125174944-11ba4961dae9 to v1.1.0 is noted. This change is generally positive, as it moves from a beta version to a stable release, which could include bug fixes and performance improvements. However, it's crucial to ensure compatibility with the Cosmos SDK store v2 module and to conduct thorough testing to verify that no breaking changes or incompatibilities have been introduced.

store/go.sum (1)

• 51-52: The update of the github.com/cosmos/iavl dependency from v1.0.0-beta.1.0.20240125174944-11ba4961dae9 to v1.1.0 is correctly reflected in the go.sum file, with the appropriate checksums added for the new version. This change aligns with the PR objectives to update the IAVL dependency used in the store v2 module.