Problem: versiondb needs go mod tidy

[yihuang]

👮🏻👮🏻👮🏻 !!!! REFERENCE THE PROBLEM YOUR ARE SOLVING IN THE PR TITLE AND DESCRIBE YOUR SOLUTION HERE !!!! DO NOT FORGET !!!! 👮🏻👮🏻👮🏻

PR Checklist:

• Have you read the CONTRIBUTING.md?
• Does your PR follow the C4 patch requirements?
• Have you rebased your work on top of the latest master?
• Have you checked your code compiles? (make)
• Have you included tests for any non-trivial functionality?
• Have you checked your code passes the unit tests? (make test)
• Have you checked your code formatting is correct? (go fmt)
• Have you checked your basic code style is fine? (golangci-lint run)
• If you added any dependencies, have you checked they do not contain any known vulnerabilities? (go list -json -m all | nancy sleuth)
• If your changes affect the client infrastructure, have you run the integration test?
• If your changes affect public APIs, does your PR follow the C4 evolution of public contracts?
• If your code changes public APIs, have you incremented the crate version numbers and documented your changes in the CHANGELOG.md?
• If you are contributing for the first time, please read the agreement in CONTRIBUTING.md now and add a comment to this pull request stating that your PR is in accordance with the Developer's Certificate of Origin.

Thank you for your code, it's appreciated! :)

Summary by CodeRabbit

• Chores
  • Updated Go version from 1.22 to 1.22.7.
  • Updated toolchain version from go1.22.9 to go1.23.1.

[coderabbitai]

Walkthrough

The pull request updates the go.mod file for the github.com/crypto-org-chain/cronos/versiondb module. It modifies the Go version from 1.22 to 1.22.7 and the toolchain version from go1.22.9 to go1.23.1. The dependencies listed in the require section remain unchanged, while the replace directives continue to redirect specific dependencies to designated versions or local paths, particularly for cosmossdk.io/store and github.com/cosmos/cosmos-sdk.

Changes

File	Change Summary
versiondb/go.mod	- Updated Go version from 1.22 to 1.22.7 - Updated toolchain version from go1.22.9 to go1.23.1 - No changes to dependencies' versions or structure in require and replace sections.

Possibly related PRs

• Problem: "mempool is full" log flood in benchmark #1599: This PR updates the Go version in the go.mod file, which is directly related to the Go version update in the main PR.
• Problem: cosmos-sdk x/tx not up to date #1638: This PR also updates the Go version in the go.mod file and includes changes to the replace directives, which aligns with the modifications made in the main PR.
• Problem: iavl pruning bug fix not included #1673: This PR updates the go.mod file with a new version for the iavl dependency, which is relevant as it involves changes to the dependency management similar to those in the main PR.

Suggested reviewers

• leejw51crypto
• devashishdxt
• mmsqe

🐇 In the garden, I hop with glee,
Versions updated, oh what a spree!
Go's now sprightly, fresh, and bright,
Toolchains dancing in the moonlight.
Dependencies steady, all in their place,
A joyful leap in this coding space! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between f7cfc3a and cf04125.

📒 Files selected for processing (1)

• versiondb/go.mod (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• versiondb/go.mod

---

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 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 16.84%. Comparing base (f7cfc3a) to head (cf04125).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1682   +/-   ##
=======================================
  Coverage   16.84%   16.84%           
=======================================
  Files          72       72           
  Lines        6161     6161           
=======================================
  Hits         1038     1038           
  Misses       5000     5000           
  Partials      123      123