chore: bump go version

[Vritra4]

Description

identical with initia-labs/initia#346

---

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, you can find examples of the prefixes below:

• confirmed ! in the type prefix if API or client breaking change
• targeted the correct branch
• provided a link to the relevant issue or specification
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• 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

This release includes essential internal updates focused on maintaining a robust system foundation. We've updated our platform and refined dependency management to boost overall stability and compatibility. While these changes are behind the scenes, they contribute to a smoother, more reliable user experience.

• Chores
  • Updated Go version to 1.23.6 for enhanced performance.
  • Cleaned up dependency versions for improved stability.
  • Updated base images in the Dockerfile for better compatibility.

[coderabbitai]

Walkthrough

The go.mod file has been updated to use a newer Go version (from 1.23.3 to 1.23.6) and a corresponding toolchain upgrade (from go1.23.5 to go1.23.6). Additionally, the replace directives have been changed so that dependencies for cometbft, ibc-go, and go-ethereum now point to custom forks hosted under github.com/initia-labs. No new dependencies were introduced, and the require block remains largely unchanged except for potential version detail updates. The integration-tests/go.mod file reflects similar updates, including version cleanups for kvindexer dependencies.

Changes

File	Change Summary
go.mod	Updated Go version (1.23.3 → 1.23.6) and toolchain (go1.23.5 → 1.23.6); modified replace directives to point cometbft, ibc-go, and go-ethereum to custom forks under github.com/initia-labs.
integration-tests/go.mod	Updated Go version (1.23.5 → 1.23.6); cleaned up kvindexer dependencies by updating versions to stable releases without timestamps.
Dockerfile	Updated base images for Go builder (golang:1.23-alpine3.19 → golang:1.23-alpine3.20) and final image (alpine:3.19 → alpine:3.20).

Possibly related PRs

• bump evm-tx submodule #60: The changes in the main PR and the retrieved PR are related as both involve updates to the go.mod file, specifically concerning the evm-tx submodule version.
• bump: opinit to v0.6.2 & cometbft & use latest ilvl #135: The changes in the main PR regarding the updates to the cometbft dependency are directly related to the modifications in the retrieved PR, which also updates the cometbft dependency version.
• chore: bump kvindexer and submodules #155: The changes in the main PR regarding the updates to the go.mod file and the modifications to the dependencies are directly related to the changes in the retrieved PR, which also focuses on updating the kvindexer and its submodules in the go.mod file.

Suggested reviewers

• beer-1

Poem

Hoppity hops through version lands,
With lines of go.mod twinkling like stars,
Custom forks lead the playful dance,
My whiskers twitch at these codeyard bars,
A rabbit’s cheer for changes that shine afar!

---

📜 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 dc7483b and ef9e914.

📒 Files selected for processing (1)

• Dockerfile (2 hunks)

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

• Dockerfile

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: golangci-lint
• GitHub Check: Minitiad
• GitHub Check: Analyze (go)

---

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

[beer-1]

LGTM