chore: prepare v7.2.0

[dadamu]

Description

Closes: #XXXX

---

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
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• 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 ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

Summary by CodeRabbit

• New Features

  • Introduced support for version 7.2.0 upgrade, enhancing the upgrade management capabilities of the application.
  • Implemented a new upgrade handler for seamless transitions within the Desmos ecosystem.

• Chores

  • Updated dependencies to improve functionality and security, including cosmos-sdk to version v0.47.13 and wasmvm to version v1.5.3.

[coderabbitai]

Walkthrough

This update introduces version 7.2.0 to the Desmos application, enhancing upgrade capabilities through the addition of a new upgrade handler and updating critical dependencies. Notable changes include the registration of the v7.2.0 upgrade handler and the introduction of an Upgrade struct to manage the upgrade process. These enhancements reflect ongoing maintenance and improvements in functionality, ensuring smoother transitions within the application.

Changes

File	Change Summary
CHANGELOG.md	Added entry for version 7.2.0, updated cosmos-sdk to v0.47.13 and wasmvm to v1.5.3.
app/upgrades.go	Registered new upgrade handler for version 720, enhancing upgrade management capabilities.
app/upgrades/v720/upgrade.go	Introduced Upgrade struct with methods for the v7.2.0 upgrade, implementing necessary upgrade logic.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant App
    participant UpgradeManager

    User->>App: Request Upgrade to v7.2.0
    App->>UpgradeManager: Initiate Upgrade Process
    UpgradeManager->>Upgrade: Create Upgrade Instance
    Upgrade->>UpgradeManager: Return Upgrade Logic
    UpgradeManager->>App: Execute Upgrade Logic
    App-->>User: Upgrade Complete

Loading

Poem

🐰 In a meadow bright, our code takes flight,
With upgrades so swift, it's a wondrous sight!
Dependencies fresh, the app's heart will race,
Hopping along, in this digital space.
A toast to the team, for the changes so grand,
Together we grow, like a garden so planned! 🌼

---

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.

[github-actions]

👀 Docs preview available here: https://66b4b9be73f2f6fdb10c74a6--desmos-docs.netlify.app

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f6e7642 and 5b07600.

Files selected for processing (3)

• CHANGELOG.md (1 hunks)
• app/upgrades.go (1 hunks)
• app/upgrades/v720/upgrade.go (1 hunks)

Files skipped from review due to trivial changes (1)

• CHANGELOG.md

Additional comments not posted (2)

app/upgrades.go (1)

6-13: LGTM! The addition of the v720 upgrade handler is consistent.

The new upgrade handler for version 720 is added correctly, following the existing pattern. The imports are updated appropriately.

app/upgrades/v720/upgrade.go (1)

1-46: LGTM! The new upgrade handler for v7.2.0 is well-structured.

The Upgrade struct and its methods are correctly implemented, adhering to the upgrades.Upgrade interface. The no-op migration is appropriate if no changes are needed.