fix: fix the canon 4 upgrade

[gsk967]

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
• added appropriate labels to the PR
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• 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 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 a new upgrade handler for version "v6.7.0-rc1".
  • Added support for multiple upgrade versions, including "v6.6", "v6.4", "v6.0", and "v4.3", ensuring smooth transitions and parameter updates during upgrades.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes introduce new upgrade handlers for the Umee application, specifically for version "v6.7.0-rc1". This includes the addition of the registerUpgrade method and multiple upgrade methods for earlier versions, ensuring that various parameters and modules are correctly managed during upgrades. The modifications also involve updating parameters related to leverage and metoken settings, as well as handling migrations and store adjustments for different versions.

Changes

File	Change Summary
app/upgrades.go	- Added registerUpgrade method for version "v6.7.0-rc1". - Added methods for upgrades "v6.6", "v6.4", "v6.0", and "v4.3" with specific logic for parameter updates and migrations.

Possibly related PRs

• feat: adding upgrade handler v6.7-rc1 for canon-4 #2616: The main PR introduces a new upgrade handler for version "v6.7.0-rc1", while this retrieved PR adds a handler for "v6.7-rc1", indicating a direct connection in the upgrade process.
• chore: v6.7.0 stable release upgrade handler #2622: This PR updates the upgrade handler to reflect the stable release of version "v6.7.0", which is a continuation of the changes made in the main PR regarding the upgrade registration process.

Suggested labels

skip-e2e-test

Suggested reviewers

• abdulgig

Poem

🐇 In the meadow, upgrades bloom,
With handlers ready to make room.
From "v6.0" to "v6.7", they dance,
Ensuring all have a fair chance.
Hopping along, we celebrate,
A brighter future, we anticipate! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 86d1a23 and b8aa1b4.

📒 Files selected for processing (1)

• app/upgrades.go (1 hunks)

---

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 generate docstrings to generate docstrings for this PR. (Experiment)
• @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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 62.00%. Comparing base (7f05ad4) to head (b8aa1b4).
Report is 557 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #2641       +/-   ##
===========================================
- Coverage   75.38%   62.00%   -13.39%     
===========================================
  Files         100      275      +175     
  Lines        8025    19628    +11603     
===========================================
+ Hits         6050    12171     +6121     
- Misses       1589     6685     +5096     
- Partials      386      772      +386     

Files with missing lines	Coverage Δ
app/upgrades.go	44.37% <100.00%> (ø)

... and 215 files with indirect coverage changes