Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): bump github.com/cosmos/ibc-go/v8 from 8.0.0 to 8.3.1 #649

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 22, 2024

Bumps github.com/cosmos/ibc-go/v8 from 8.0.0 to 8.3.1.

Release notes

Sourced from github.com/cosmos/ibc-go/v8's releases.

v8.3.1

This release improves the performance in the handling of MsgRecvPacket and MsgUpdateClient in the RedundantRelayDecorator ante handler.

Please check the v8.3.1 changelog for more details.


To learn more about ibc-go versioning, please read our RELEASES.md.

IMPORTANT: Please read the migration guides for any versions of ibc-go that you might be going through when upgrading to this version. For example: if you upgrade from the IBC module contained in the Cosmos SDK 0.42.0 to SDK v0.50.6 and ibc-go v8.3.1, please follow:

  1. The migration from SDK 0.41.x or 0.42.x to the IBC module in the ibc-go repository based on the SDK v0.44.x.
  2. The migration from ibc-go v1 to v2.
  3. The migration from ibc-go v2 to v3.
  4. The migration from ibc-go v3 to v4.
  5. The migration from ibc-go v4 to v5.
  6. The migration from ibc-go v5 to v6.
  7. The migration from ibc-go v6 to v7.
  8. The migration from ibc-go v7 to v7.1.
  9. The migration from ibc-go v7.2 to v7.3.
  10. The migration from ibc-go v7 to v8.
  11. The migration from ibc-go v8 to v8.1.

v8.3.0

Highlights 🌟

We present here a summary of the most relevant changes, please see the v8.3.0 changelog for the full set of changes included in this release. Check out also the release announcement blog post for more information.

dependencies

  • Cosmos SDK has been bumped to v0.50.6.
  • CometBFT has been bumped to v0.38.7.

core

  • Up until now ibc-go assumed that its underlying consensus is Tendermint, but in this release we have added the ConsensusHost interface that defines methods to validate an IBC light client ClientState and ConsensusState against the host chain's underlying consensus parameters. This enables chains whose underlying consensus is not Tendermint to still use ibc-go and be able to specify how the client state and consensus state of counterparties' light clients should be verified during the connection handshake. A custom implementation of the ConsensusHost interface can be set in the core IBC keeper using function SetConsensusHost. By default the consensus host will be set to the implementation for 07-tendermint. See issue cosmos/ibc-go#5315 and PR cosmos/ibc-go#6055 for more details.

core/02-client

  • We have added the VerifyMembershipProof query service gRPC endpoint that queries an IBC light client for proof verification of a value at a given key path. This endpoint specifically enables light clients to query other light clients through gRPC, and streamlines the process of implementing conditional clients, particularly within the 08-wasm module. The method takes a QueryVerifyMembershipRequest where the ID of the light client the verification parameters (proof, value, height, etc) are specified. See issue cosmos/ibc-go#5310 and PR cosmos/ibc-go#5821 for more details.

apps/transfer

  • In v8.1.0 the field allowed_packet_data was added to the Allocation type used for authz support of IBC transfers. This field was originally a list of MsgTransfer's memo packet data keys that were allowed (i.e. top level JSON object keys). After receiving some feedback (thanks to Yieldmos team), we have re-purposed this field to be a list of full memo strings. That means that this field contains a list of memo strings that that the granter allows the grantee to include in the memo field of MsgTransfer, the grantee can then submit MsgTransfer with one of the allowed memo strings. See the documentation for more information.
  • In OnChanOpenTry, when the counterparty version does not match the executing chain's own version, instead of returning an error, the current version is now returned. This allows the channel handshake to complete in situations where the handshake initiating chain has the fee middleware wired up, but the counterparty doesn't (then transfer channel will be created with a version that does not contain fee middleware information). Similar change has been applied to OnChanOpenTry of the host submodule in 27-interchain-accounts. See PR cosmos/ibc-go#6253 for more details.

apps/27-interchain-accounts

Unordered channels

... (truncated)

Changelog

Sourced from github.com/cosmos/ibc-go/v8's changelog.

v8.3.1 - 2024-05-22

Improvements

  • (core/ante) #6302 Performance: Skip app callbacks during RecvPacket execution in checkTx within the redundant relay ante handler.
  • (core/ante) #6280 Performance: Skip redundant proof checking in RecvPacket execution in reCheckTx within the redundant relay ante handler.
  • (core/ante) #6306 Performance: Skip misbehaviour checks in UpdateClient flow and skip signature checks in reCheckTx mode.

v8.3.0 - 2024-05-16

Dependencies

  • #6300 Bump Cosmos SDK to v0.50.6 and CometBFT to v0.38.7.

State Machine Breaking

  • (light-clients/07-tendermint) #6276 Fix: No-op to avoid panicking on UpdateState for invalid misbehaviour submissions.

Improvements

  • (apps/27-interchain-accounts, apps/tranfer, apps/29-fee) #6253 Allow channel handshake to succeed if fee middleware is wired up on one side, but not the other.
  • (apps/27-interchain-accounts) #6251 Use UNORDERED as the default ordering for new ICA channels.
  • (apps/transfer) #6268 Use memo strings instead of JSON keys in AllowedPacketData of transfer authorization.
  • (core/ante) #6278 Performance: Exclude pruning from tendermint client updates in ante handler executions.

Features

  • (core) #6055 Introduce a new interface ConsensusHost used to validate an IBC ClientState and ConsensusState against the host chain's underlying consensus parameters.
  • (core/02-client) #5821 Add rpc VerifyMembershipProof (querier approach for conditional clients).
  • (core/04-channel) #5788 Add NewErrorAcknowledgementWithCodespace to allow codespaces in ack errors.
  • (apps/27-interchain-accounts) #5785 Introduce a new tx message that ICA host submodule can use to query the chain (only those marked with module_query_safe) and write the responses to the acknowledgement.

Bug Fixes

  • (apps/27-interchain-accounts) #6167 Fixed an edge case bug where migrating params for a pre-existing ica module which implemented controller functionality only could panic when migrating params for newly added host, and align controller param migration with host.
  • (app/29-fee) #6255 Delete refunded fees from state if some fee(s) cannot be refunded on channel closure.

v8.2.0 - 2024-04-05

Dependencies

  • #5975 Bump Cosmos SDK to v0.50.5.

Improvements

  • (proto) #5987 Add wasm proto files.

v8.1.0 - 2024-01-31

Dependencies

... (truncated)

Commits
  • 9b6567b update changelog before v8.3.1 release
  • bcd74b7 imp: add updateClientCheckTx to redunant relayer ante decorator (backport #62...
  • e18de37 perf: minimize logic on rechecktx for recvpacket (backport #6280) (#6344)
  • 611a9a3 perf: minimize necessary execution on recvpacket checktx (backport #6302) (#6...
  • 30a03a3 perf: exclude pruning from tendermint update client in ante handler execution...
  • f6fe145 Update CHANGELOG.md
  • 8b708ca update changelog before v8.3.0 release
  • 0b10c11 deps: bump cosmos sdk to v0.50.6 and comet bft to v0.38.7 (#6300)
  • 41b6a00 Update CHANGELOG.md
  • 5470cd2 imp: allow memo strings instead of keys for transfer authorizations (backport...
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels May 22, 2024
@dependabot dependabot bot requested review from amimart and ccamel May 22, 2024 10:06
Copy link
Contributor

coderabbitai bot commented May 22, 2024

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.


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

@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/cosmos/ibc-go/v8-8.3.1 branch from f3db2f4 to db8531b Compare May 24, 2024 10:12
@bdeneux
Copy link
Contributor

bdeneux commented May 31, 2024

See cosmos/ibc-go#6435

updated-dependencies:
- dependency-name: github.com/cosmos/ibc-go/v8
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/cosmos/ibc-go/v8-8.3.1 branch from db8531b to cb3852b Compare June 4, 2024 13:28
Copy link
Contributor Author

dependabot bot commented on behalf of github Jun 20, 2024

Superseded by #681.

@dependabot dependabot bot closed this Jun 20, 2024
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/cosmos/ibc-go/v8-8.3.1 branch June 20, 2024 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants