Skip to content

[stable2603] Backport #11496#11501

Open
paritytech-release-backport-bot[bot] wants to merge 2 commits intostable2603from
backport-11496-to-stable2603
Open

[stable2603] Backport #11496#11501
paritytech-release-backport-bot[bot] wants to merge 2 commits intostable2603from
backport-11496-to-stable2603

Conversation

@paritytech-release-backport-bot

Backport #11496 into stable2603 from tdimitrov.

See the documentation on how to use this bot.

…ocol (#11496)

When starting the node with a warp sync and we hit a period near the
`WARP_SYNC_TARGET_BLOCK` (each 512 blocks) we might not be able to call
a runtime apis for some blocks, which will yield an error in the
collator protocol revamp.

Don't bubble up such errors to prevent the subsystem from exiting.

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
(cherry picked from commit 9d8a2fe)
@github-actions github-actions bot added the A3-backport Pull request is already reviewed well in another branch. label Mar 25, 2026
@github-actions github-actions bot requested a review from tdimitrov March 25, 2026 13:55
@github-actions
Copy link
Contributor

This pull request is amending an existing release. Please proceed with extreme caution,
as to not impact downstream teams that rely on the stability of it. Some things to consider:

  • Backports are only for 'patch' or 'minor' changes. No 'major' or other breaking change.
  • Should be a legit fix for some bug, not adding tons of new features.
  • Must either be already audited or not need an audit.
Emergency Bypass

If you really need to bypass this check: add validate: false to each crate
in the Prdoc where a breaking change is introduced. This will release a new major
version of that crate and all its reverse dependencies and basically break the release.

@EgorPopelyaev EgorPopelyaev enabled auto-merge (squash) March 25, 2026 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A3-backport Pull request is already reviewed well in another branch.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants