You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The next regular release will be v0.32.0 with some important updates for IBC "on packet receive" logic and CosmWasm v1.3 v1.2.3 that will take some time.
While we make progress on the sdk 47 path, we plan to tag more release candidates to enable other teams to start integration and testing early. There is still a bigger packet of work with v1.gov support.
As you may have noticed, there are some gabs between v0.32 and v0.40. Our versioning model does not support breaking changes well, so we have some numbers reserved for releases on the v0.45.x path.
What comes next
It is hard to maintain 2 versions in parallel with a small team. The plan is to focus on the sdk v0.47 path for new features after our v0.32.0. Bugfixes and security updates will be backported to the sdk v0.45 path for some time.
Please join the discussion
The text was updated successfully, but these errors were encountered:
I have updated the target WasmVm version to v1.2.3 due to some unexpected issues with the integration of the wasmer version. This will unblock the v0.32 release and also reduces the changes and therefore risk that come with v0.40.
We plan to release another wasmd version (v0.33) with wasmvm v1.3 on the sdk 45 series as maintenance release. New features go to the sdk 47 series and may only be backported on specific request.
There were some updates posted on our discord before but it is useful to share the plan in the repo, too:
The release plan
We are working on 2 milestones currently.
releases/v0.3x
branchmain
branchThe next regular release will be v0.32.0 with some important updates for IBC "on packet receive" logic and CosmWasm
v1.3v1.2.3 that will take some time.While we make progress on the sdk 47 path, we plan to tag more release candidates to enable other teams to start integration and testing early. There is still a bigger packet of work with v1.gov support.
As you may have noticed, there are some gabs between v0.32 and v0.40. Our versioning model does not support breaking changes well, so we have some numbers reserved for releases on the v0.45.x path.
What comes next
It is hard to maintain 2 versions in parallel with a small team. The plan is to focus on the sdk v0.47 path for new features after our v0.32.0. Bugfixes and security updates will be backported to the sdk v0.45 path for some time.
Please join the discussion
The text was updated successfully, but these errors were encountered: