chore: skip upgrade handler on testnet

[zakir-code]

Summary by CodeRabbit

• New Features

  • Added specific handling for Testnet environments in the upgrade process, ensuring that upgrades are skipped when operating on Testnet.

• Bug Fixes

  • Enhanced test stability by explicitly setting the chain ID in the upgrade migration tests.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The recent changes enhance the handling of upgrades within the application by introducing specific checks for the Testnet environment. The modifications ensure that critical upgrade processes are conditionally bypassed when running in a test environment. This approach improves the robustness of the upgrade functionality, ensuring that it behaves predictably under different chain conditions, particularly for testing scenarios.

Changes

File Path	Change Summary
app/upgrade_test.go	Added a call to fxtypes.SetChainId(chainId) in the Test_UpgradeAndMigrate function to explicitly set the chain ID for consistent test behavior.
app/upgrades/v7/constants.go	Introduced a conditional statement in StoreUpgrades to return an empty struct for Testnet environments, altering control flow based on the chain ID.
app/upgrades/v7/upgrade.go	Added a check in CreateUpgradeHandler to skip the upgrade process if the chain ID corresponds to Testnet, preventing any migration logic from executing.

Sequence Diagram(s)

sequenceDiagram
    participant Test as Test Suite
    participant UpgradeHandler as Upgrade Handler
    participant StoreUpgrades as Store Upgrades

    Test->>StoreUpgrades: Call with Chain ID
    alt Testnet Chain ID
        StoreUpgrades-->>Test: Return empty struct
    else Other Chain
        StoreUpgrades-->>UpgradeHandler: Proceed with upgrades
    end
    UpgradeHandler->>Test: Return version map

Loading

🐇 In the meadow where upgrades bloom,
A rabbit hops, dispelling gloom.
Testnet's path is clear and bright,
With checks in place, all feels just right.
Upgrades now dance with a structured grace,
In our code's heart, they find their place! 🌼✨

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.