Skip to content

Conversation

@paritytech-release-backport-bot

Backport #10232 into stable2503 from BDevParity.

See the documentation on how to use this bot.

paritytech/release-engineering#265

---------

Co-authored-by: Egor_P <egor@parity.io>
(cherry picked from commit d6cb9dc)
@github-actions github-actions bot added the A3-backport Pull request is already reviewed well in another branch. label Nov 20, 2025
@github-actions github-actions bot requested a review from BDevParity November 20, 2025 14:42
@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