-
Notifications
You must be signed in to change notification settings - Fork 101
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
Remove DMP Queue and Allow system::authorize_upgrade
in XCM
#280
Remove DMP Queue and Allow system::authorize_upgrade
in XCM
#280
Conversation
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.
Good! I see the other system parachains already have it on the safe list 👍
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.
In which context is this used?
Upgrading parachains |
/merge |
Enabled Available commands
For more information see the documentation |
@joepetrowski You need to remove the |
Head branch was pushed to by a user without write access
system::authorize_upgrade
in XCMsystem::authorize_upgrade
in XCM
Don't we need to add migration
like Basti did here: https://github.com/polkadot-fellows/runtimes/pull/277/files#diff-da00a6055ce091ceb6769ed5cc0dc6527aca586de0394a60aa3d18c38ff89716R140 for AssetHubs and BridgeHubs ? |
@bkchr @kianenigma @acatangiu @muharem can you take another look? Larger changes since just adding these two calls to the filter. |
/merge |
5cf99f3
into
polkadot-fellows:main
Enabled Available commands
For more information see the documentation |
Allow using
system::authorize_upgrade
asparachain_system
's is deprecated.