Skip to content

[stable2506] Backport #11631#11669

Merged
EgorPopelyaev merged 1 commit intostable2506from
backport-11631-to-stable2506
Apr 7, 2026
Merged

[stable2506] Backport #11631#11669
EgorPopelyaev merged 1 commit intostable2506from
backport-11631-to-stable2506

Conversation

@paritytech-release-backport-bot
Copy link
Copy Markdown

Backport #11631 into stable2506 from BDevParity.

See the documentation on how to use this bot.

…y are triggered manually and not with the workflow_call trigger (#11631)

paritytech/release-engineering#291
(cherry picked from commit 20d65ad)
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 7, 2026

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 Apr 7, 2026
@EgorPopelyaev EgorPopelyaev enabled auto-merge (squash) April 7, 2026 15:15
@paritytech-review-bot paritytech-review-bot Bot requested a review from a team April 7, 2026 15:15
@EgorPopelyaev EgorPopelyaev merged commit f191993 into stable2506 Apr 7, 2026
320 of 324 checks passed
@EgorPopelyaev EgorPopelyaev deleted the backport-11631-to-stable2506 branch April 7, 2026 15:18
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