Handler for 0.2 upgrade #28
Merged
Conversation
This file contains 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
rkollar
approved these changes
Dec 8, 2024
|
@luckychess please add a description for what this PR does and also whether the CI tests are enough or whether we should test anything specifically about the changes being introduced. |
lukitsbrian
reviewed
Dec 11, 2024
lukitsbrian
approved these changes
Dec 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds update handler from 0.1 to 0.2.
Tested locally and in staging.
To test, an old SSC instance (v0.1 aka mainnet v1) should be started, then a governance proposal should be submitted (the name is
0.1-to-0.2). After the chain halt, the old sscd binary should be replaced with the new version (0.2) and then after the chain restart (just a normalsscd start) this update will be applied automatically.