search

confio / tgrade

The Tgrade Blockchain Binary, based on the Cosmos SDK and wasmd
Apache License 2.0
31 stars 10 forks source link

Bump github.com/cosmos/ibc-go/v3 from 3.3.0 to 3.4.0 #477

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 2 years ago

Bumps github.com/cosmos/ibc-go/v3 from 3.3.0 to 3.4.0.

Release notes

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

v3.4.0

This release uses Cosmos SDK v0.45.10 and introduces a couple of improvements requested by the community. Please see the v3.4.0 changelog for more details.

apps/transfer

  • The sequence number of the packet sent has been added to MsgTransferResponse.
  • An optional memo field has been added to FungibleTokenPacketData. Token transfers that include a non-empty memo field will fail if the receiver chain is not running a version of ibc-go that also supports the memo field. Please read this blog post for more information.

apps/27-interchain-accounts

  • The check in OnChanOpenTry callback on the host submodule that required the port ID on the controller chain to be prefixed by icacontroller- has been removed. Thanks to @​LaurensKubat and @​catShaark for this recommendation.

Special thanks to our external contributors on this release: @​faddat @​agouin @​nicolaslara @​LaurensKubat

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.45.10 and ibc-go v3.4.0, 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 to add support for transfers of tokens whose base denomination contains slashes.

v3.3.1

This release bumps the Cosmos SDK from v0.45.8 to v0.45.10. Cosmos SDK v0.45.10 includes the fix for the dragonberry security advisory.

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.45.10 and ibc-go v3.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 to add support for transfers of tokens whose base denomination contains slashes.
Changelog

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

v3.4.0 - 2022-11-07

Dependencies

  • #2589 Bump SDK version to v0.45.10 and Tendermint to v0.34.22.

State Machine Breaking

  • (apps/transfer) #2651 Introduce mustProtoMarshalJSON for ics20 packet data marshalling which will skip emission (marshalling) of the memo field if unpopulated (empty).
  • (27-interchain-accounts) #2580 Removing port prefix requirement from the ICA host channel handshake
  • (transfer) #2377 Adding sequence to MsgTransferResponse.

Features

  • (apps/transfer) #2595 Adding optional memo field to FungibleTokenPacketData and MsgTransfer.

Bug Fixes

  • (apps/transfer) #2672 Check x/bank send enabled.

v3.3.1 - 2022-10-27

Dependencies

  • #2621 Bump SDK version to v0.45.10 and Tendermint to v0.34.22.
Commits
  • d409970 typo in tag link
  • 9571a79 prepare changelog for v3.4.0 release
  • b36dc31 add check send enabled (backport #2679) (#2688)
  • 3a2244b fix: skip emission of unpopulated memo field in ics20 (backport #2651) (#2653)
  • 79a10f0 release/v3.4.x: bump to SDK v0.45.10 (#2589)
  • ffc5a79 remove port prefix requirement (backport #2590) (#2632)
  • 68845e5 use controller module address instead of module name for NewMsgChannelOpenIni...
  • 0089c93 refactor: adapting transfer metadata bytes field to memo string (backport #25...
  • 048d80f add entry for #2305
  • be0902c Added optional packet metadata to the packet and message types (backport #230...
  • Additional commits viewable in compare view


Dependabot compatibility score

You can trigger a rebase of this PR 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 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)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

dependabot[bot] commented 1 year ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.