-
Notifications
You must be signed in to change notification settings - Fork 124
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
[Manta] Integrate v0.9.13
upstream changes
#294
Conversation
v0.9.13
upstream changes
Because we're going to support rust 2021, so perhaps we have to add a icon or section in readme to tell users the MSRV(minimum supported Rust version), it should be |
Thanks, please let me know if this is enough in the README |
…a-Network/Manta into ghzlatarev/polkadot-v0.9.13
Can you also take a look at the runtime upgrade failure? |
This is a rococo and 0.9.12 issue. |
Description
closes: #293
closes: #271
closes #306
Manta Changes
validation_delay_upgrade
of 20 blocks in polkadot-launch configsClient
parachain-id
cli command paritytech/cumulus#739Runtime
PalletsOrigin
topallet_utility
which allows Root to become any other origin type, such as collectives - council , technical committee, etc. implement dispatch_as paritytech/substrate#9934OriginPrivilegeCmp
topallet_scheduler
to make sure that a council origin with more yes votes has higher privileges than a council origin with less yes votes. IntroduceOriginPrivilegeCmp
paritytech/polkadot#4166AllowSubscriptionsFrom
- allowSubscribeVersion
orUnsubscribeVersion
instructions fromParentOrSiblings
AllowSubscriptionsFrom
- allows messages which arePendin
orVersionNotifier
responses to queries.Upstream Changes
Polkadot Changes:
OriginPrivilegeCmp
paritytech/polkadot#4166Release Checklist:
Substrate Changes:
trie_root_hash
variant for chain specs genesis paritytech/substrate#10140staking::reap_stash
paritytech/substrate#10178pallet-asset-tx-payment
from cumulus to substrate paritytech/substrate#10127--detailed-log-output
flag paritytech/substrate#10278clean_shutdown
paritytech/substrate#10314Cumulus Changes:
parachain-id
cli command paritytech/cumulus#739dispatch_as
paritytech/cumulus#715statemine diffs between:
c02514d8cb66d6860e597f75d53ca07119dbbf32-> 0.9.12
0be8e8fc214641e306e4f913dd64ff1913e46e95 -> 0.9.13
Tests (Local --> Baikal)
QA Tests (Local)
https://hackmd.io/TbFmorG2RnOPmLuFcg9JOQ?view
Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
manta
ordolphin
) with right title (start with [Manta] or [Dolphin]),Files changed
in the Github PR explorer.authoring_version
: The version of the authorship interface. An authoring node will not attempt to author blocks unless this is equal to its native runtime.spec_version
: The version of the runtime specification. A full node will not attempt to use its native runtime in substitute for the on-chain Wasm runtime unless all of spec_name, spec_version, and authoring_version are the same between Wasm and native.impl_version
: The version of the implementation of the specification. Nodes are free to ignore this; it serves only as an indication that the code is different; as long as the other two versions are the same then while the actual code may be different, it is nonetheless required to do the same thing. Non-consensus-breaking optimizations are about the only changes that could be made which would result in only the impl_version changing.transaction_version
: The version of the extrinsics interface. This number must be updated in the following circumstances: extrinsic parameters (number, order, or types) have been changed; extrinsics or pallets have been removed; or the pallet order in the construct_runtime! macro or extrinsic order in a pallet has been changed. If this number is updated, then the spec_version must also be updatedversion
for every crate.BaseFilter
. Ensure every extrinsic works from front-end. If there's corresponding tool, ensure both work for each other.