v0.46.0 Release

[robert-zaremba]

Summary

Tracking issue for 0.46.0.

v0.46 Release team: @AmauryM @robert-zaremba @marbar3778

Before beta release

These are the pieces that need to be merged before we tag a beta.

• Transaction tips & tx middleware #9557
• Gov/Group minimal alignment
• Fix authz time.Now() non-determinism for v0.46 #11115
• feat: add timepb support library cosmos-proto#60
• Update authz expire to make it optional #11095
• feat(authz)!: pruning expired authorizations #10714
• feat: adds pruning for feegrant #10830
• tag IAVL 0.18
• update SDK to IAVL 0.18
• feat(types): Deprecate the DBBackend variable in favor of new app-db-backend config entry #11188
• Renamed store/v2 -> store/v2alpha1 #11378
• fix: authz with denylist #11403
• refactor(x/auth/middleware)!: tx middleware to support pluggable feemarket module #11413

nice to have

• Add rollback support in the event of an incorrect hash #10281
• feat!: deprecate auth/types.NewModuleAddress #11141

beta release

This phase is focused on v0.46 auditing. Once we move into this phase, we create a new branch release/v0.46.x. PRs are to be merged into master and backported to release/v0.46.x. Features, client-breaking changes and small API-breaking changes can still be merged back into the release branch if deemed necessary.

• Create a release/v0.46.x branch
• Tag beta1 off release/v0.46.x.
• Release Readiness of new features
  • Transaction Tips & Middlewares Readiness Checklist #11087
  • x/gov v1 Module Readiness Checklist #11086
  • Group Module - Module Readiness Checklist #10968
• v045..v046 Audit changes on existing code #11362
• Run devnets & testnets (if bandwidth allows)
  • TODO Subsection to be filled with external orgs & chains committing to test the beta release
• Ensure documentation for all new features is up-to-date.
  • Update docs for Check/DeliverTx middlewares #9954
  • Docs on using tipped transactions #10426
• Note: Multiple beta releases can be tagged if needed.
• In the case where both following conditions are met: 1/ a significant number of PRs are merged into master between two RC releases and 2/ all these PRs should be backported; then the release team can decide to reset --hard the release/v0.46.x branch to point to master.
• Reset the release/v0.46.x branch to main @marbar3778

RC Blockers:

• refactor: Revert middlewares to antehandlers (part 1/2: baseapp) #11979
• refactor: Revert middlewares to antehandler (part 2/2: posthandler) #11985
• confirm posthandler/tips decisions are okay: refactor: Revert middlewares to antehandler (part 2/2: posthandler) #11985 (comment)
• feat: Cancel unbonding delegation entry #10885
• Revert using a global legacy.Cdc for all modules #11643

nice to haves:

• Pre-upgrade/key migration is not working tendermint/tendermint#7737
• chore: migrate to cosmos-gogo #11414
• fix: rollback command don't actually delete multistore versions #11361
• refactor!: abstractions for snapshot and pruning; snapshot intervals eventually pruned; unit tests #11496

rc release

Unless there's a strong requirement otherwise, this phase should be focused on bugfixes, final polishes and testnet/devnet testing. PRs are to be merged into master and backported to release/v0.46.x. Client-breaking changes and small API-breaking changes can still be merged back into the release branch if deemed necessary.

• Add a 0.46.0-rc1 section on master's CHANGELOG @AmauryM chore: Add v0.46.0 RC1 release notes and changelog #12015
• Write RELEASE_NOTES.md @AmauryM chore: Add v0.46.0 RC1 release notes and changelog #12015
• Tag off rc1 from the release branch.
• Audit Changelog against commit log, ensuring all breaking changes, bug fixes, and improvements are properly documented. @AmauryM
  • Did not do a thorough audit (too long), but a quick scan.
• Create a UPGRADING.md document #11587 Update UPGRADING.md
• Make sure all CI sims pass
• Run devnets & testnets
  • Manual Testing for v0.46 #11880
  • Subsection to be filled with external orgs & chains committing to test the rc release
    • Vitwit
    • IG @marbar3778
    • Network stops producing blocks after upgrade from v0.45.x to v0.46.0-rc1 #12041
• Note: Multiple rc releases can be tagged if needed.
• In the case where both following conditions are met: 1/ a significant number of PRs are merged into master between two beta releases and 2/ all these PRs should be backported; then the release team can decide to reset --hard the release/v0.46.x branch to point to master.

v0.46.0 release

• Merge all Changelog entries from all rc releases into one v0.46.0 section
• Merge and synthetize RELEASE_NOTES.md from all rc releases
• Tag off v0.46.0 from the release/v0.46.x branch.
• Update the STABLE_RELEASES.md document
• Verify and update general docs: docs.cosmos.network documentation tracking #11898
• Ensure docs.cosmos.network has a v0.46 branch
• Create new Cosmovisor release

[faddat]

Hi all, it looks like Notional is going to invest heavily in SDK v46, because:

• Better testnet features for easier development
• libp2p & ipld in tendermint 35
• NFTs
• Work on governance, against the latest iteration

I'd like to tell you about how I am thinking about constructing stacks with SDK 46, and would love comment.

Right now, I've got testnets blocked by:

• wasmd imports ibc so I am upgrading ibcv3 to support sdk 46

In fact, that might kind of be all. The way that I have been approaching developing on this version, fully aware that there may be issues from upstream, is to update the chain daily, and I've got testing set up with the new "testnet start" command (guys, this is gold)

I think we may be able to help solve a problem.

I think the sdk is flourishing
I think ibc-go is flourishing

I think they've lost touch with one another compatibility wise and that's inevitable.

I also think that cw will see really wide adoption, and I'd like to use it in a number of upcoming projects, so I'm going to get a thing going that will test:

• wasmd
• ibc-go
• all of the modules in the sdk

and it occurs to me that the test platform I described there, also makes a very good template.

To build craft I used simapp as a reference very often and I got it to a place where I felt very good about its no-ibc stability.

I'm now trying to add CW (/x/wasm) to craft and that is getting tough.

Anyhow, I think that I'll iron out any issues pretty quickly and that we will soon have something that pulls all of these together.

Here are my earliest observations:

• Simapp is cool, but isn't a template
• Starport is cool, but doesn't really keep pace with the sdk (not a criticism, there's reason for this of course)
• ibc-go is needed for meaningful testing
• wasm shall be de rigeur -- whatever that means :P

Would the SDK team like a PR of:

• an application template?
• A system for testing the latest versions of all the things against one another?
• none of the above?

It could also possibly live in its own repository.

Thanks very much

PS, I just thought of something that may make what I am describing clearer:

a template with

• latest sdk (the tip, currently v0.46.0-alpha2 but really talking about the master branch)
• latest ibc-go (currently v3.0.0-rc1)
  • support for cosmos-sdk v0.46.0-alpha2 ibc-go#949
• latest /x/wasm (currently v0.23.0)
  • CW + SDK v46 + ibcv3 CosmWasm/wasmd#764

in a ci system that

• monitors the different repositories
• builds each time there's a change to the master branch
• provides the community with integration information

PS:

This isn't really a feature request, and is certainly not a complaint. It is more or less what I figure I'll build and would love to get feedback on.

I know everyone is super-strapped for time and resources. The needs of our clients & communities have brought this to the front for us, and if we end up doing the various upgrades, we surely don't mind :).

[cyborgshead]

I hope state rollback will be merged soon, waiting for this feature for years
Sad to see this is nice to have in last releases for a far time

[faddat]

osmosis-labs/osmosis#705

I'm pretty sure that the capabilities needed for interfluid staking start with something like ica+46+cw

[amaury1093]

Just tagged v0.46.0-beta1.