v0.52.0

Wasmd v0.52.0 Release

See the CHANGELOG for details on the changes in this version.

v0.51.0

Wasmd v0.51.0 Release

See the CHANGELOG for details on the changes in this version.

v0.50.0

Wasmd v0.50.0 Release

See the CHANGELOG for details on the changes in this version.

Big thanks to all the people who helped us with this release! 😍 Especially Binary Builders, Notional and the IBC-Go team 💪
And not to forget our sponsors. 🤗

v0.45.0

Wasmd v0.45.0 Release

See the CHANGELOG for details on the changes in this version.

v0.44.0

Wasmd v0.44.0 Release

See the CHANGELOG for details on the changes in this version.

v0.43.0

Wasmd v0.43.0 Release

See the CHANGELOG for details on the changes in this version.

v0.42.0

Wasmd v0.42.0 Release

See the CHANGELOG for details on the changes in this version.

🚨 This version includes CosmWasm v1.4 and is retracted. We are investigating a RuntimeError: out of bounds memory access issue when upgrading a chain from CosmWasm v1.3. See https://twitter.com/CosmWasm/status/1709507168448229497

v0.41.0

Wasmd v0.41.0 Release

See the CHANGELOG for details on the changes in this version.

v0.40.1

This patch release includes only the wasmvm upgrade to v1.2.4.
It solves some incompatibility problems by improving cache invalidation. See CosmWasm/wasmvm#426

Notable changes

• Upgrade wasmvm to v1.2.4 (#1430)

Migration notes

• This release does not include any state migrations or breaking changes, therefore a coordinated chain upgrade is not required.

v0.40.0

First release on the SDK 47 series. Please make sure to read the Changelog carefully.

Notable changes:

• If you are not coming from v0.32.0, please see the "Notables changes" of that release, first. Especially about CometBFT.
• IBC-Go is a new major version including the "hucklebery" security fix. See v7.0.1.
• SDK 47 support is a big step from the SDK 45 version supported before. Make sure to read the upgrade guide for the SDK
  before applying any changes. Links below.
• Some advice from working with SDK 47 that may affect you, too:
  • The SDK version includes some key store migration for the CLI. Make sure you backup your private keys before
    testing this! You can not switch back to v0.45 afaik
  • Take care that you use the goleveldb version used in the SDK. A transitive dependency may change it which caused
    failing queries on a running server: Error: rpc error: code = InvalidArgument desc = failed to load state at height 1; version does not exist (latest height: 1): invalid request
    Ensure this in go.mod:
    github.com/syndtr/goleveldb => github.com/syndtr/goleveldb v1.0.1-0.20210819022825-2ae1ddf74ef7
  • With custom modules, use the new proto-builder version (Makefile) to let proto types register with the correct registry
  • Ensure that all ParameterChangeProposal are completed before the upgrade or migrate them to v1.gov. SDK and wasm
    modules execute a migration before so that these proposals would not have an affect.
  • Attribute keys/ values in events are strings and not bytes in CometBFT. This may break clients
  • CLI: add-genesis-account, gentx,add-genesis-account, collect-gentxs and others are now under genesis command as parent
  • CLI: --broadcast-mode block was removed. You need to query the result for a TX with wasmd q tx <hash> instead

Migration notes:

• This release contains a state migration for the wasmd module that stores
  the params in the module store.
• SDK v0.47 comes with a lot of api/state braking changes to previous versions. Please see their upgrade guide
  which contains a lot of helpful details.
• Please read the migration guide for IBC-Go v7.0.0 carefully