You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
Similar to what was done for paritytech/pipeline-scripts#23, in case a Substrate PR has companions on Polkadot and Cumulus, it's not enough to update only Substrate for Cumulus: the Polkadot PR should be updated into the Cumulus PR as well.
Instead of the current:
Merge Substrate PR
Update lockfile of Polkadot and Cumulus
Wait to merge
It should be
Merge Substrate PR
Update the lockfile of the Polkadot PR
Wait for Polkadot PR to be merged
Update the lockfile of Cumulus with both Substrate and Polkadot
Merge Cumulus PR
The text was updated successfully, but these errors were encountered:
This is yet another "companion build system design problem" to add onto #327.
Showcased by the interaction between paritytech/substrate#10463, paritytech/polkadot#4519 and paritytech/cumulus#870.
Similar to what was done for paritytech/pipeline-scripts#23, in case a Substrate PR has companions on Polkadot and Cumulus, it's not enough to update only Substrate for Cumulus: the Polkadot PR should be updated into the Cumulus PR as well.
Instead of the current:
It should be
The text was updated successfully, but these errors were encountered: