Port safe commits from master to polkadot-staging #2761
Merged
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.
opening early for visibility - could be reviewed commit-by-commit
Since we are now closer to moving to
polkadot-sdk
than to developingbridges-v2
+ some parts of v2 have been already merged to thepolkadot-staging
, maybe we should start picking some commits from master and merge them topolkadot-staging
. I'll start with safe commits that are not touching any critical code pieces. The final goal is to have #2457 inpolkadot-staging
- it'll should make bridges configuration much easier. So in next updates of polkadot-sdk and fellowship runtimes we'll decrease LOCs dedicated to bridges configuration.All
v2
stuff (dynamic lanes, relayers protocol) will stay in master.Additionally, it'll make backporting easier - right now not having #2171 and #2181 in
polkadot-staging
is painful