Skip to content

Conversation

@paritytech-release-backport-bot

Backport #10280 into stable2506 from bkchr.

See the documentation on how to use this bot.

@paritytech-release-backport-bot
Copy link
Author

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

git fetch origin backport-10280-to-stable2506
git worktree add --checkout .worktree/backport-10280-to-stable2506 backport-10280-to-stable2506
cd .worktree/backport-10280-to-stable2506
git reset --hard HEAD^
git cherry-pick -x 4e1d96383b2ae73de8e66ac9f8c8b8580ac9af80
git push --force-with-lease

@github-actions github-actions bot added the A3-backport Pull request is already reviewed well in another branch. label Nov 11, 2025
@github-actions github-actions bot requested a review from bkchr November 11, 2025 21:50
@bkchr bkchr marked this pull request as ready for review November 12, 2025 19:49
@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.

@paritytech-workflow-stopper
Copy link

All GitHub workflows were cancelled due to failure one of the required jobs.
Failed workflow url: https://github.com/paritytech/polkadot-sdk/actions/runs/19313237881
Failed job name: test-linux-stable

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