Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[meta] strict on-runtime-upgrade CI checks to prevent accidental runtime upgrade breakages #481

Closed
8 of 9 tasks
liamaharon opened this issue Jun 26, 2023 · 1 comment
Closed
8 of 9 tasks

[meta] strict on-runtime-upgrade CI checks to prevent accidental runtime upgrade breakages #481

liamaharon opened this issue Jun 26, 2023 · 1 comment
Assignees
@liamaharon
Labels
I6-meta A specific issue for grouping tasks or bugs of a specific category.

Comments

@liamaharon
Copy link
Contributor

liamaharon commented Jun 26, 2023 •
edited
Loading

try-runtime-cli on-runtime-upgrade has stabilised over the last few months to that point where we can add CI checks to ensure Polkadot & Substrate PRs don't accidentally break upcoming polkadot/kusama/rococo/westend runtime upgrades

Creating a meta issue to track this progress.

Remaining TODOs:

After some time has passed and we are confident in the robustness of the CI checks:
@liamaharon liamaharon self-assigned this Jun 26, 2023
This was referenced Jul 2, 2023
Merged
Merged
@liamaharon liamaharon mentioned this issue Jul 12, 2023
Merged
1 task
@liamaharon liamaharon mentioned this issue Jul 24, 2023
Merged
@juangirini juangirini transferred this issue from paritytech/polkadot Aug 24, 2023
@the-right-joyce the-right-joyce added I6-meta A specific issue for grouping tasks or bugs of a specific category. and removed J1-meta labels Aug 25, 2023
@liamaharon
Copy link
Contributor Author

Done

@github-project-automation github-project-automation bot moved this from In Progress to Done in Runtime / FRAME Oct 23, 2023
jonathanudd pushed a commit to jonathanudd/polkadot-sdk that referenced this issue Apr 10, 2024
@HCastano @bkchr
Allow Substrate Pallet to be Initialized via Dipatchable (paritytech#481
cac8319 
)

* Add dispatchable for intializing pallet

* Add Polkadot JS types for Substrate bridge pallet

* Ensure Root is the only one that can initialize the pallet

* Add some tests

* Pack initialization data into struct

* Only allow pallet to be initialized once

* Use new initialization config in nodes

* Rename ScheduledChange in Ethereum pallet

We're renaming it to prevent clashes with Substrate bridge pallet type
of the same name. This is relevant when importing types to Polkadot JS
Apps.

* Move all Polkadot JS types into one file

* Appease Clippy
This was referenced Jun 5, 2024
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@liamaharon liamaharon

Labels
I6-meta A specific issue for grouping tasks or bugs of a specific category.
Projects
Runtime / FRAME
Status: Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@liamaharon @the-right-joyce