Releases: cosmos/ibc-go
v3.2.0
UPDATES
- 27th October 2022: This release is NOT recommended since it uses a version of the Cosmos SDK impacted by the dragonberry security advisory. Please use version >= 3.3.1.
- 20th September 2022: It is NOT recommended to use the ICS27 host submodule of this release, since it contains a security vulnerability. Please use version >= 3.3.0.
Please note that, according to ibc-go's semantic versioning, this release requires a coordinated upgrade because it contains state-machine breaking changes. This release requires also running a migration.
This release bumps the Go version to v1.18 and the Cosmos SDK to v0.45.7 (for more information, see Cosmos SDK v0.45.7 Release Notes), and introduces several improvements and bug fixes. We present here a summary of the most relevant changes. Please see the v3.2.0 changelog for the full set of changes included in this release.
apps/transfer
- A new migration has been added to correct any malformed trace path information of tokens whose base denomination contains slashes. The transfer module consensus version has been bumped to 2.
- The channel ID is now used to split the complete denomination into the trace path and the base denomination. Previously the port ID
transfer
was used. - A check has been added to ensure that the sender is not a blocked address. Thanks to @asalzmann for reporting a problem with blocked addresses that resulted in this fix.
light-clients/07-tendermint
- Client upgrade proposals are now able to update the
TrustingPeriod
of the light client.
Special thanks to our external contributors on this release: @pyramation @devashishdxt @joeabbey
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.6 and ibc-go v3.2.0, please follow:
v2.4.0
UPDATES
- 27th October 2022: This release is NOT recommended since it uses a version of the Cosmos SDK impacted by the dragonberry security advisory. Please use version >= 2.4.2.
Please note that, according to ibc-go's semantic versioning, this release requires a coordinated upgrade because it contains state-machine breaking changes. This release requires also running a migration.
This release bumps the Go version to v1.18 and the Cosmos SDK to v0.45.7 (for more information, see Cosmos SDK v0.45.7 Release Notes), and introduces several improvements and bug fixes. We present here a summary of the most relevant changes. Please see the v2.4.0 changelog for the full set of changes included in this release.
apps/transfer
- A new migration has been added to correct any malformed trace path information of tokens whose base denomination contains slashes. The transfer module consensus version has been bumped to 2.
- The channel ID is now used to split the complete denomination into the trace path and the base denomination. Previously the port ID
transfer
was used. - A check has been added to ensure that the sender is not a blocked address. Thanks to @asalzmann for reporting a problem with blocked addresses that resulted in this fix.
light-clients/07-tendermint
- Client upgrade proposals are now able to update the
TrustingPeriod
of the light client.
Special thanks to our external contributors on this release: @pyramation @devashishdxt @joeabbey
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.6 and ibc-go v2.4.0, please follow:
v4.0.0-rc3
This release includes v1 of the Fee Middleware module. 🍾 Please read the introduction blog post and the documentation!
It also bumps the Go version to v1.18 and the Cosmos SDK to v0.45.7 (for more information, see Cosmos SDK v0.45.7 Release Notes), and introduces several improvements and bug fixes. We present here a summary of the most relevant changes in comparison to v4.0.0-rc2. Please see the v4.0.0 changelog for the full set of changes included in this pre-release.
dependencies
- The Cosmos SDK has been bumped from v0.45.6 to v0.45.7.
apps/transfer
- A check has been added to ensure that the sender is not a blocked address. Thanks to @asalzmann for reporting a problem with blocked addresses that resulted in this fix.
apps/29-fee
- A check has been added in the rpc handlers for
MsgPayPacketFee
andMsgPayPacketFeeAsync
to ensure that the escrow address is not blocked. A similar check has also been added to the rpc handler forMsgRegisterPayee
to ensure that the payee address is not blocked.
Special thanks to our external contributors on this release: @faddat @vuong177 @devashishdxt
This is potentially the last RC before the final v4.0.0 release. If no issues are found, we are planning to create the final release at the end of the week.
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.6 and ibc-go v4.0.0-rc3, please follow:
v3.1.1
UPDATES
- 27th October 2022: This release is NOT recommended since it uses a version of the Cosmos SDK impacted by the dragonberry security advisory. Please use version >= 3.3.1.
- 20th September 2022: It is NOT recommended to use the ICS27 host submodule of this release, since it contains a security vulnerability. Please use version >= 3.3.0.
This release bumps the Cosmos SDK to v0.45.5 (for more information, see Cosmos SDK v0.45.5 Release Notes) and introduces a couple of improvements. Please see the v3.1.1 changelog for more details.
Special thanks to our external contributors on this release: @pyramation
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.5 and ibc-go v3.1.1, please follow:
v3.0.2
UPDATES
- 27th October 2022: This release is NOT recommended since it uses a version of the Cosmos SDK impacted by the dragonberry security advisory. Please use version >= 3.3.1.
- 20th September 2022: It is NOT recommended to use the ICS27 host submodule of this release, since it contains a security vulnerability. Please use version >= 3.3.0.
This release introduces a couple of improvements. Please see the v3.0.2 changelog for more details.
Special thanks to our external contributors on this release: @pyramation
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.4 and ibc-go v3.0.2, please follow:
v2.3.1
UPDATES
- 27th October 2022: This release is NOT recommended since it uses a version of the Cosmos SDK impacted by the dragonberry security advisory. Please use version >= 2.4.2.
This release bumps the Cosmos SDK to v0.45.5 (for more information, see Cosmos SDK v0.45.5 Release Notes) and introduces a couple of improvements. Please see the v2.3.1 changelog for more details.
Special thanks to our external contributors on this release: @pyramation
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.5 and ibc-go v2.3.1, please follow:
v2.2.2
UPDATES
- 27th October 2022: This release is NOT recommended since it uses a version of the Cosmos SDK impacted by the dragonberry security advisory. Please use version >= 2.4.2.
This release introduces a couple of improvements. Please see the v2.2.2 changelog for more details.
Special thanks to our external contributors on this release: @pyramation
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.1 and ibc-go v2.2.2, please follow:
v2.1.2
UPDATES
- 27th October 2022: This release is NOT recommended since it uses a version of the Cosmos SDK impacted by the dragonberry security advisory. Please use version >= 2.4.2.
This release introduces a couple of improvements. Please see the v2.1.2 changelog for more details.
Special thanks to our external contributors on this release: @pyramation
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.44.8 and ibc-go v2.1.2, please follow:
v5.0.0-beta1
This release bumps the Cosmos SDK to v0.46 (for more information, see Cosmos SDK v0.46 Release Notes) and Tendermint to v0.34.20 (for more information, see Tendermint 0.34.20 changelog). It also introduces several code style improvements flagged by linting tools. Please see the v5.0.0 changelog for the full set of changes included in this pre-release.
Special thanks to our external contributors on this release: @faddat
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.46 and ibc-go v5.0.0-beta1, please follow:
- 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.
- The migration from ibc-go v1 to v2.
- The migration from ibc-go v2 to v3.
- The migration from ibc-go v3 to v4.
- The migration from ibc-go v4 to v5 (not available yet, but work is in progress here).
v4.0.0-rc2
This release includes v1 of the Fee Middleware module. 🍾 Please read the introduction blog post and the documentation!
It also bumps the Go version to v1.18 and the Cosmos SDK to v0.45.6 (for more information, see Cosmos SDK v0.45.6 Release Notes), and introduces several improvements and bug fixes. We present here a summary of the most relevant changes in comparison to v4.0.0-rc1. Please see the v4.0.0 changelog for the full set of changes included in this pre-release.
core/03-connection
- The
PreviousConnectionID
argument has been removed fromNewMsgConnectionOpenTry
.MsgConnectionOpenTry.ValidateBasic()
returns now an error if the deprecatedPreviousConnectionID
is not empty.
core/04-channel
- The
PreviousChannelID
argument has been removed fromNewMsgChannelOpenTry
.MsgChannelOpenTry.ValidateBasic()
returns now an error if the deprecatedPreviousChannelID
is not empty.
apps/29-fee
- The import/export for genesis upgrades has been fixed.
Special thanks to our external contributors on this release: @faddat @vuong177
This is potentially the last RC before the final v4.0.0 release. If no issues are found, in approximately two weeks the final release will be created.
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.6 and ibc-go v4.0.0-rc2, please follow: