Skip to content

Conversation

@paritytech-release-backport-bot

Backport #10792 into stable2512 from bkchr.

See the documentation on how to use this bot.

When issuing a `force_reserve` we are putting the reservation into the
current and next region `WorkPlan`. The issue is that at the next sale
rotation we override all unused cores. As the sale rotation isn't aware
of the forcefully registered core, also the force reserved core is
overwritten and the parachain looses their coretime for one region (it
comes back in the next region). To fix this we now keep track of
forcefully registered reserves. We input them alongside the other
reservations into the workplan, but for the current region using any
free cores from the previous sale.

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Dónal Murray <[email protected]>
(cherry picked from commit 84064c9)
@paritytech-release-backport-bot paritytech-release-backport-bot bot requested a review from a team as a code owner January 14, 2026 22:18
@github-actions github-actions bot added the A3-backport Pull request is already reviewed well in another branch. label Jan 14, 2026
@github-actions github-actions bot requested a review from bkchr January 14, 2026 22:18
@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.

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