chore: update ethermint

[dreamer-zq]

Summary by CodeRabbit

• Dependency Updates
  • Updated ethermint dependency to a newer version
  • Modified cosmossdk.io/api replacement directive

[coderabbitai]

Walkthrough

The pull request focuses on updating dependency versions in the go.mod file for the github.com/irisnet/irishub/v4 module. The primary changes involve updating the version of github.com/evmos/ethermint to a newer commit and maintaining the existing cosmossdk.io/api replacement directive. These modifications aim to align the project's dependencies with the latest available versions while preserving the overall dependency structure.

Changes

File	Change Summary
go.mod	- Updated github.com/evmos/ethermint version from v0.22.0-irishub-20240512.0.20250102063401-4dfa00763ed4 to v0.22.0-irishub-20240512.0.20250103062036-dc2ecd5cc643

Possibly related PRs

• refactor: bump up irismod #2950: Updates to go.mod file involving dependency version modifications

Suggested reviewers

• harvey-smith
• mitch1024

Poem

🐰 Dependency dance, a version's new stance,
Ethermint leaps with a git-powered prance!
Modules align, code's rhythm so fine,
A rabbit's update, a technical sign! 🚀
Go forth, new version, your journey begins!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 691b281 and 78da990.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (1)

• go.mod (1 hunks)

🔇 Additional comments (2)

go.mod (2)

271-271: LGTM! The ethermint update follows the established pattern.

The change maintains the existing versioning scheme and uses the same fork as before, just updating to a newer commit. The explicit version pinning helps ensure reproducible builds.

---

271-271: Verify the stability of the new ethermint commit.

The update to v0.22.0-irishub-20240512.0.20250103062036-dc2ecd5cc643 appears to be a minor change (from Jan 2nd to Jan 3rd commit). Let's verify the commit's stability and changes.

✅ Verification successful

The new ethermint commit appears stable and includes a necessary interface implementation

The commit message indicates a clear, focused change: "evm and feemarket module must implement beginBlocker and endBlocker interface". This is a structural improvement ensuring proper interface implementation, which is a good sign for stability.

Let's verify if there are any breaking changes or significant modifications in the codebase:

---

The ethermint update is verified and appears safe to merge

The changes between the commits are well-scoped and focused on implementing the required BeginBlocker and EndBlocker interfaces in the EVM and FeeMarket modules. The modifications affect:

• Implementation files for ABCI interfaces
• Module definitions
• Keeper implementations

Key observations:

• Changes are contained to expected module files
• Direct parent-child relationship between commits indicates clean history
• Recent commit timestamp (Jan 3rd, 2025) shows it's the latest update
• No breaking changes detected in the scope of modifications

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the ethermint dependency commit

# Check if the commit exists and get its details
gh api \
  -H "Accept: application/vnd.github+json" \
  repos/bianjieai/ethermint/commits/dc2ecd5cc643 \
  --jq '.commit.message'

# Check for any related issues or PRs mentioning potential issues with this commit
gh api \
  -H "Accept: application/vnd.github+json" \
  search/issues \
  -f q='repo:bianjieai/ethermint dc2ecd5cc643 type:issue state:open' \
  --jq '.items[].title'

Length of output: 545

---

Script:

#!/bin/bash
# Check the diff between the old and new commits
gh api \
  -H "Accept: application/vnd.github+json" \
  repos/bianjieai/ethermint/compare/4dfa00763ed4...dc2ecd5cc643 \
  --jq '.files[].filename'

# Get the commit details to check if it's part of a PR
gh api \
  -H "Accept: application/vnd.github+json" \
  repos/bianjieai/ethermint/commits/dc2ecd5cc643 \
  --jq '{author: .commit.author.name, date: .commit.author.date, parents: [.parents[].sha]}'

Length of output: 539

---

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>, please review it.
  • Generate unit testing code 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 testing code 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.