Closed
Conversation
kvinwang
reviewed
Jan 18, 2023
d28917f to
fbf848a
Compare
kvinwang
reviewed
Jan 19, 2023
ac87c64 to
a6d2683
Compare
1d29978 to
e1236f4
Compare
Contributor
Author
|
Close in favor of #1129 |
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
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.34...polkadot-v0.9.35
paritytech/substrate@polkadot-v0.9.35...polkadot-v0.9.36
Breaking changes for us:
mem_infoand references toparity-util-memparitytech/substrate#12795Special note for paritytech/substrate#12891 in the future, we have to write
call_indexfor every extrinsic calls, or it will fail to compilationOther notable changes:
EnsureOriginOrHigherPrivilegeparitytech/substrate#12844TODO: These Subxt change breaks Pherry
api.blocks()to be the primary way to subscribe and fetch blocks/extrinsics/events paritytech/subxt#691RpcErrorwith custom client error paritytech/subxt#694