chore(deps): Bump to Cosmos-SDK v0.50.7-kyve-rc0

[mbreithecker]

Summary by CodeRabbit

• Chores

  • Updated to CosmosSDK v0.50.7.
  • Ensured release builds are reproducible.
  • Only charging coins that are whitelisted.

• Refactor

  • Rearranged import statements in the integration test helpers.

[coderabbitai]

Walkthrough

The recent updates include upgrading to CosmosSDK v0.50.7, transitioning the inflation-share-weight in x/pool to a decimal format, ensuring reproducible release builds, and enforcing charges only for whitelisted coins. Additionally, minor import rearrangements were made in the helpers.go file within the testutil/integration package.

Changes

File	Change Summary
CHANGELOG.md	Bumped CosmosSDK dependency to v0.50.7, adjusted inflation-share-weight to decimal, ensured reproducible builds, and restricted charges to whitelisted coins.
testutil/integration/helpers.go	Rearranged import statements for "cosmossdk.io/math" and "github.com/KYVENetwork/chain/x/global/types".

Poem

Amidst the code, a change so bright,
CosmosSDK shines its light.
Decimal weights now take their place,
Ensuring builds with steady grace.
Whitelisted coins, the only fare,
A cleaner path, beyond compare.

---

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 Configration 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.

[coderabbitai]

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 57153a6 and ba7661d.

Files ignored due to path filters (5)

• go.mod is excluded by !**/*.mod
• go.sum is excluded by !**/*.sum
• go.work.sum is excluded by !**/*.sum
• interchaintest/go.mod is excluded by !**/*.mod
• interchaintest/go.sum is excluded by !**/*.sum

Files selected for processing (1)

• CHANGELOG.md (1 hunks)

Additional context used

LanguageTool

CHANGELOG.md

[style] ~103-~103: Using many exclamation marks might seem excessive (in this case: 25 exclamation marks for a text that’s 11971 characters long) (EN_EXCESSIVE_EXCLAMATION)
Context: ...de auth module. ### Client Breaking - ! (x/stakers) [#46](https://github.com/...

[coderabbitai]

Actionable comments posted: 0

Outside diff range and nitpick comments (8)

testutil/integration/helpers.go (8)

Line range hint 12-17: Consider adding a comment explaining why panic is used here, as it helps in understanding that this is intended to halt test execution on critical errors.

---

Line range hint 19-27: Consider enhancing error handling by logging or other mechanisms instead of silently returning an empty coin set, which could obscure underlying issues.

---

Line range hint 29-37: Improve error visibility by adding logging when an error occurs in address parsing or balance retrieval.

---

Line range hint 39-47: Add error logging to provide more context when an error occurs, which could be crucial for debugging.

---

Line range hint 49-57: Enhance error handling by logging when the pool is not found, to aid in troubleshooting.

---

Line range hint 59-63: Consider adding error handling for cases where GetModuleAccount might fail, to ensure robustness.

---

Line range hint 65-69: Add error handling for potential failures in retrieving module account details.

---

Line range hint 71-89: Improve error handling by checking for failures in GetBundleProposal and handling them appropriately.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ba7661d and 7659c7c.

Files ignored due to path filters (3)

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

Files selected for processing (1)

• testutil/integration/helpers.go (1 hunks)

Additional comments not posted (1)

testutil/integration/helpers.go (1)

6-7: The rearrangement of imports looks good and should help in maintaining a cleaner codebase.