-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: [v2.0.x] upgrade cosmos-sdk to v0.45.4 #466
Conversation
// registerUpgradeHandlers registers upgrade handlers, and sets the store loader if necessary. | ||
// This function must be called before sealing the BaseApp (i.e. by app.LoadLatestVersion()) | ||
// because the storetypes loader cannot be set if BaseApp is already sealed. | ||
func (app *App) registerUpgradeHandlers() error { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we upgrade our mainnet to v2.0.5 with this upgrade handler, I think we must remove the upgrade handler in the master
branch which is similar as this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
When upgrading to v0.45.9, configuration for grpc web is added to |
Yeah. I'll put a note in the gov proposal, that the grpc-web will be enabled by default. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
This PR is supposed to be merged to the
release/v2.0.x
branch, and be released with the tagv2.0.5
after some additional PRs are merged as well.Just cherry-picked from 664d546
TODO: should be tested if the chain can be upgraded smoothly from 2.0.3 to 2.0.5 without hard forks