Bump SDK - Always Reset OE

[teddyding]

Changelist

Bump SDK to adopt this change. Non-breaking change for OE, completely no-op for nodes not enabling OE.

Test Plan

Stably running on prod FNS full node

Author/Reviewer Checklist

• If this PR has changes that result in a different app state given the same prior state and transaction list, manually add the state-breaking label.
• If the PR has breaking postgres changes to the indexer add the indexer-postgres-breaking label.
• If this PR isn't state-breaking but has changes that modify behavior in PrepareProposal or ProcessProposal, manually add the label proposal-breaking.
• If this PR is one of many that implement a specific feature, manually label them all feature:[feature-name].
• If you wish to for mergify-bot to automatically create a PR to backport your change to a release branch, manually add the label backport/[branch-name].
• Manually add any of the following labels: refactor, chore, bug.

Summary by CodeRabbit

• Chores
  • Updated dependency versions to ensure compatibility with the latest features and fixes.
  • Adjusted module replacements to utilize customized versions of critical libraries.

[teddyding]

@Mergifyio backport release/protocol/v6.x

[mergify]

backport release/protocol/v6.x

✅ Backports have been created

• #2532 Bump SDK - Always Reset OE (backport #2531) has been created for branch release/protocol/v6.x

[teddyding]

@Mergifyio backport release/protocol/v7.x

[mergify]

backport release/protocol/v7.x

✅ Backports have been created

• #2533 Bump SDK - Always Reset OE (backport #2531) has been created for branch release/protocol/v7.x

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The go.mod file for the github.com/dydxprotocol/v4-chain/protocol module has been updated to reflect changes in dependency versions and replacements. Key updates include a new version for github.com/cosmos/cosmos-sdk and several replace directives that point to specific versions of dependencies, including customized forks. The modifications ensure compatibility with the latest features and fixes while maintaining the overall structure of the dependency declarations.

Changes

File

Change Summary

protocol/go.mod

- Updated github.com/cosmos/cosmos-sdk from v0.50.6-0.20240808180557-4b1c1dc17703 to v0.50.6-0.20241022180223-cc8c850952c5 - Replaced dependencies: cosmossdk.io/client/v2 → github.com/cosmos/cosmos-sdk/client/v2 v2.0.0-beta.1.0.20240219091002-18ea4c520045 cosmossdk.io/core → cosmossdk.io/core v0.11.0 cosmossdk.io/store → github.com/dydxprotocol/cosmos-sdk/store v1.0.3-0.20240326192503-dd116391188d github.com/cometbft/cometbft → github.com/dydxprotocol/cometbft v0.38.6-0.20241001172045-cfee87f3abbf github.com/cosmos/iavl → github.com/dydxprotocol/iavl v1.1.1-0.20240509161911-1c8b8e787

Possibly related PRs

• [OTE-53] Bump cosmos-sdk fork version (Abort OE in PrepareProposal) #1950: This PR updates the version of the github.com/dydxprotocol/cosmos-sdk dependency, which is directly related to the version update in the main PR.
• Bump Cosmos SDK version  #2064: This PR also updates the github.com/dydxprotocol/cosmos-sdk dependency to a newer version, aligning with the changes made in the main PR.
• chore: Bump Cometbft to log proposer when proposal is rejected #2421: This PR includes updates to dependencies related to the Cosmos SDK and CometBFT, which are also modified in the main PR, indicating a connection in the dependency management.

Suggested labels

backport/protocol/v6.x

Suggested reviewers

• jonfung-dydx
• vincentwschau

🐇 In the meadow, I hop with glee,
Dependencies updated, oh what a spree!
With forks and versions, we dance and play,
Ensuring our protocol shines every day.
Hopping along, we’re ready to deploy,
A brighter future, oh what joy! 🌼

---

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.