Releases: CosmWasm/wasmd
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 tov1.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 withwasmd q tx <hash>
instead
- The SDK version includes some key store migration for the CLI. Make sure you backup your private keys before
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
v0.14.0: Opening the Stargate
This is the first wasmd release built on Cosmos SDK v0.40.0
final, aka Stargate. It is fully compatible with the IBC version to be deployed on the Cosmos Hub (and many other networks in Q1 2021 and beyond).
It also included and updated wasmer virtual machine, wasmer v1.0.0
, with improved performance and stability.
We will be adding more IBC features in the next few releases, but you can already transfer tokens from other chains and use them in your contracts.
v0.13.0
v0.13.0 (2020-11-30)
Fixed bugs:
- REST handler wrong
Sender
source #324
Closed issues:
- Change proto package to match <organisation>.<module>.<version> #329
- Out of gas causes panic when external contract store query executed #321
- Check codecov report #298
- cosmwasm.GoAPI will not work on sdk.ValAddress #264
- Stargate: Add pagination support for queries #242
Merged pull requests:
v0.11.0
Feature complete for 1.0
This is the tag for coralnet
and gaiaflex
and is a feature-complete system. We will do a major upgrade on the wasm engine and bugfixes before 1.0, and clean up some APIs, but no more major features will be added (except directly related to the wasm engine upgrade)
Ready to try out and build your contracts against.