Bump cosmossdk.io/client/v2 from 2.0.0-beta.4 to 2.0.0-beta.5

[dependabot]

Bumps cosmossdk.io/client/v2 from 2.0.0-beta.4 to 2.0.0-beta.5.

Commits

• 25255e4 feat(client/v2): use x/tx AminoNameAsTypeURL option in 0.50 (#21801)
• 7ee3115 feat(x/tx): add aminoNameAsTypeURL option in aminojson encoder (backport #2...
• f812291 chore: prepare v0.50.10 (#21498)
• b2ec2f6 fix(runtime): fix option order (backport #21769) (#21771)
• 9a0a76f docs(x/circuit): display correct example (backport #21768) (#21773)
• 3feb2c0 docs: demonstrate how to wire custom ante handlers in 0.50 app_di (#21767)
• b21441c feat(types/collections): add LegacyDec collection value (backport #21693) (...
• f78ed49 feat(x/genutil): add better error messages for genesis validation (backport #...
• fe37dfb docs(x/authz): update grant docs (backport #21677) (#21700)
• ef8a575 docs(client/debug): correct debug raw-bytes command example (backport #2167...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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

[SpicyLemon]

Ugh... Breaking 3rd party protobuf change due to the bump in ics23/go.

Error: Enum value "3" on enum "HashOp" changed name from "KECCAK" to "KECCAK256".
Error: buf found 1 breaking changes.

I'm not sure what we can do about that, so I'm gonna hold off on this PR for a bit.

There's a good chance that we just accept it and move forward, but we need to consider the ramifications first.

[SpicyLemon]

Created cosmos/ics23#376 to let them know about the breaking change. We'll wait on that a bit before deciding what to do here.

[SpicyLemon]

Two things combine to make it very likely that this won't cause a problem:

1. There are no known uses of KECCAK yet.
2. The only thing that can fail because of this is client creation as that's the only thing with one of these fields that might be communicated as JSON instead of protobuf.

Also, there isn't really a way to fix this since the updated proto is already out there; changing it back would cause another breaking change for anyone using this version.

So we really only have two options:

1. Accept this PR and just live with the breaking change (that probably won't cause any problems anyway).
2. Never update that library again.

Option 1 seems like the only realistic option to me, so I suggest we approve and merge this PR.