Rename v050 upgrade to v4.0.0 + fill real release/checksum details - #209
Merged
Conversation
….0/v3.0.0) to SDK 0.50 - v3.0.0: keep upstream name=v3.0.0, port consensus-params migration to 0.50 (collections.Item ParamStore, context.Context closure) - v2.4.0/v2.6.0: bank/auth/distr handlers to 0.50 (math.NewInt, context ctx) - v2.5.0: claim+min-commission+multisig migration to 0.50; authz/feegrant/gov-vote steps omitted (keepers no longer threaded / gov API changed) - TODO-marked - restore app/ante min_commission + min_gas_prices to 0.50 (math.Legacy*) - wire historical handlers into app.go Upgrades slice; drop v047
…es, 79/79 contracts, all migrations apply)
Author
|
Quick ask for a maintainer: could someone cut a `v4.0.x` branch off the `v3.0.0` tag (same pattern as `v3.0.x` used for #207)? `main` is stale on SDK 0.45/go1.20, and this PR is currently based on `release/v2.6.0-sdk-v047` since we don't have push access to create branches directly. Happy to retarget this PR's base to `v4.0.x` once it exists. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #208 (merged). That PR ported the 0.47->0.50 (hop-2) upgrade under the working name
v050. This PR:app/upgrades/v050->app/upgrades/v4.0.0(packagev4_0_0,const Name = "v4.0.0") to match Passage'svX.Y.Zon-chain naming convention (mainnet's live handler isv3.0.0, notv047/v050).plan.infobinaries at the published Ninjaxan/Passage3Dv4.0.0release (amd64/arm64).Why a new PR instead of amending #208
#208 was already merged into
release/v2.6.0-sdk-v047before this rename/doc work happened on our fork branch, and we don't have push access to this repo, so it has to land as its own PR.Test plan
go build ./...green on the renamed treev4.0.0name (upgrade applies, all queries pass, expedited gov params live)🤖 Generated with Claude Code