Skip to content

Conversation

@paritytech-release-backport-bot

Backport #10455 into stable2512 from EgorPopelyaev.

See the documentation on how to use this bot.

…of the released crates in release draft (#10455)

Closes: paritytech/release-engineering#276

---------

Co-authored-by: Andrei Sandu <[email protected]>
(cherry picked from commit 1e5c58b)
@github-actions
Copy link
Contributor

github-actions bot commented Dec 2, 2025

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 added the R0-no-crate-publish-required The change does not require any crates to be re-published. label Dec 4, 2025
@EgorPopelyaev EgorPopelyaev enabled auto-merge (squash) December 4, 2025 08:28
@paritytech-review-bot paritytech-review-bot bot requested a review from a team December 4, 2025 08:29
@EgorPopelyaev EgorPopelyaev merged commit 66f9354 into stable2512 Dec 4, 2025
226 of 230 checks passed
@EgorPopelyaev EgorPopelyaev deleted the backport-10455-to-stable2512 branch December 4, 2025 08:32
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. R0-no-crate-publish-required The change does not require any crates to be re-published.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants