build(deps): bump golang.org/x/sync from 0.8.0 to 0.9.0

[zakir-code]

Summary by CodeRabbit

• Chores
  • Updated dependency versions for improved compatibility and feature enhancements.
  • Introduced replacements for specific modules to utilize alternative repositories.

[coderabbitai]

Walkthrough

The pull request involves updates to the go.mod file, focusing on dependency version upgrades and the addition of replacement directives for several modules. Notably, the version of golang.org/x/sync has been updated from v0.8.0 to v0.9.0. Several dependencies have been redirected to alternative repositories, including specific forks of the Cosmos SDK and Ethereum libraries, ensuring compatibility and potentially enhancing features.

Changes

File	Change Summary
go.mod	- Updated golang.org/x/sync from v0.8.0 to v0.9.0
	- Added replacements for several dependencies:
	- cosmossdk.io/store → github.com/crypto-org-chain/cosmos-sdk/store
	- github.com/cosmos/cosmos-sdk → github.com/crypto-org-chain/cosmos-sdk
	- github.com/99designs/keyring → github.com/cosmos/keyring
	- github.com/ethereum/go-ethereum → github.com/functionx/go-ethereum
	- github.com/evmos/ethermint → github.com/pundiai/ethermint
	- github.com/cockroachdb/pebble → github.com/cockroachdb/pebble
	- github.com/syndtr/goleveldb → github.com/syndtr/goleveldb

Possibly related PRs

• build: replace with github.com/functionx/go-ethereum #588: This PR involves replacing github.com/ethereum/go-ethereum with github.com/functionx/go-ethereum, which is directly related to the changes made in the main PR regarding the same dependency.
• build(deps): bump github.com/cosmos/ibc-go/v8 from 8.5.1 to 8.5.2 #809: This PR updates the replace directive for github.com/cosmos/cosmos-sdk and github.com/ethereum/go-ethereum, which aligns with the changes in the main PR regarding these dependencies.

🐰 In the meadow where bunnies play,
New dependencies hop in today!
With forks and updates, we cheer and sing,
For smoother coding, oh what joy they bring!
Let's dance with joy, our code's in bloom,
With every change, there's more room! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 509f4cd and 07e0d46.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• go.mod (1 hunks)

🔇 Additional comments (1)

go.mod (1)

48-48: LGTM: Safe version bump of golang.org/x/sync

The update from v0.8.0 to v0.9.0 is a minor version bump which should maintain backward compatibility according to semantic versioning.

Let's verify the changelog for any breaking changes:

✅ Verification successful

Version bump of golang.org/x/sync is safe to proceed

The codebase only uses the errgroup package from golang.org/x/sync, which is a stable and well-established synchronization primitive. The package is used consistently across test and server components. Since this is a minor version bump (v0.8.0 to v0.9.0), it follows semantic versioning principles ensuring backward compatibility, and the errgroup package is known for its stability.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check the changelog between v0.8.0 and v0.9.0 of golang.org/x/sync

# Fetch the release information using GitHub API
gh api repos/golang/sync/releases \
  --jq '.[] | select(.tag_name == "v0.9.0") | .body'

Length of output: 86

---

Script:

#!/bin/bash
# Let's check the usage of golang.org/x/sync in the codebase to understand the impact
# First, find all Go files
rg -l "golang.org/x/sync" --type go

# Then check for specific sync package imports and their usage
rg "\"golang.org/x/sync/" --type go -A 2

Length of output: 850

---

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.