Skip to content

[stable2603] Backport #11056#11127

Merged
EgorPopelyaev merged 4 commits intostable2603from
backport-11056-to-stable2603
Feb 20, 2026
Merged

[stable2603] Backport #11056#11127
EgorPopelyaev merged 4 commits intostable2603from
backport-11056-to-stable2603

Conversation

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

Backport #11056 into stable2603 from BDevParity.

See the documentation on how to use this bot.

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

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin backport-11056-to-stable2603
git worktree add --checkout .worktree/backport-11056-to-stable2603 backport-11056-to-stable2603
cd .worktree/backport-11056-to-stable2603
git reset --hard HEAD^
git cherry-pick -x 8c106ffcc5174b9920a842415f84024bcb558724
git push --force-with-lease

@github-actions github-actions bot added the A3-backport Pull request is already reviewed well in another branch. label Feb 19, 2026
@github-actions github-actions bot requested a review from BDevParity February 19, 2026 16:46
EgorPopelyaev and others added 2 commits February 20, 2026 10:44
This reverts commit ecae5be.
Co-authored-by: Egor_P <egor@parity.io>
Co-authored-by: ParityReleases <release-team@parity.io>
@EgorPopelyaev EgorPopelyaev added the R0-no-crate-publish-required The change does not require any crates to be re-published. label Feb 20, 2026
@EgorPopelyaev EgorPopelyaev marked this pull request as ready for review February 20, 2026 09:45
@EgorPopelyaev EgorPopelyaev requested review from a team as code owners February 20, 2026 09:45
@EgorPopelyaev EgorPopelyaev enabled auto-merge (squash) February 20, 2026 09:45
@paritytech-review-bot paritytech-review-bot bot requested a review from a team February 20, 2026 09:46
@github-actions
Copy link
Copy Markdown
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 merged commit 9ed2595 into stable2603 Feb 20, 2026
333 of 350 checks passed
@EgorPopelyaev EgorPopelyaev deleted the backport-11056-to-stable2603 branch February 20, 2026 10:26
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