-
Notifications
You must be signed in to change notification settings - Fork 36
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: allow endblocker to update app version #321
Conversation
@@ -465,6 +465,8 @@ func (app *BaseApp) GetConsensusParams(ctx sdk.Context) *abci.ConsensusParams { | |||
cp.Validator = &vp | |||
} | |||
|
|||
cp.Version = &tmproto.VersionParams{AppVersion: app.appVersion} |
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.
nice, so now we should just be able to call app.SetVersion
instead of wrapping endblock, I can dig it
we should try to upstream this (later) |
I need to dig in to how the SDK do it now because they've made some heavy modifications in that area since v0.46 |
Codecov Report
@@ Coverage Diff @@
## release/v0.46.x-celestia #321 +/- ##
=========================================================
Coverage 65.54% 65.55%
=========================================================
Files 666 666
Lines 70983 71018 +35
=========================================================
+ Hits 46529 46553 +24
- Misses 21876 21882 +6
- Partials 2578 2583 +5
|
Ref: cosmos#16243 |
It looks like v0.47 onwards will support altering the |
Currently, I see know what that an application can use the end blocker to change the app version. All app version changes happen during a coordinated restart which means only the Info abci call is used to update the app version. This change means that the consensus param returned in EndBlock is always the applications app version. This means a module need only use SetProtocolVersion to enact a app version change in the following block