ParityTech update for April 2024

[bkchr]

@WilliamFreude

Sorry for re-rubbing salt in the wound, I just wanted to mention this to proof my point.

I get the frustration I hope this will be gone in the future!

@WilliamFreude

It is incomprehensible to me how you can be everywhere so fast and on point. Have you succeeded in cloning yourself?

I can not comment on this topic

@WilliamFreude

I would really appreciate this and I believe other parachain builders would as well, especially because it decreases likelihood of parachains missing the migration and reducing their block authors to the invulnerable set.

It was actually backported to 1.7.0: Backport 4229 Into v1.7.0 by joepetrowski · Pull Request #4288 · paritytech/polkadot-sdk · GitHub

However, it was only backported to the crates release branch (another thing that should not exist with the new release process!). I assume you used directly the release-polkadot-v1.7.0 branch? I will push the backport there, so you don’t require your manual backport.