Upgrade to Polkadot 0.9.30 #984
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
jasl
force-pushed
the
polkadot-v0.9.30
branch
3 times, most recently
from
924062a
to
18bee23
Compare
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.
paritytech/substrate@polkadot-v0.9.29...polkadot-v0.9.30
The change looks big, but most are about renaming (
Origin->RuntimeOrigin,Event->RuntimeEvent,Call->RuntimeCall)This version only upgrade WASM-relates crates, upstream should have a more widely dependencies upgrades in next release (which not get the timing for this release),
so I plan do dependencies upgrades for us in next version too
Notable changes:
I also upgrade Subxt to master latest, there's a change paritytech/subxt#680 need PhaXT do a small refactor