Skip to content

[stable2512] Backport #10459#10537

Merged
karolk91 merged 3 commits intostable2512from
backport-10459-to-stable2512
Dec 4, 2025
Merged

[stable2512] Backport #10459#10537
karolk91 merged 3 commits intostable2512from
backport-10459-to-stable2512

Conversation

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

Backport #10459 into stable2512 from karolk91.

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-10459-to-stable2512
git worktree add --checkout .worktree/backport-10459-to-stable2512 backport-10459-to-stable2512
cd .worktree/backport-10459-to-stable2512
git reset --hard HEAD^
git cherry-pick -x 34034a943bf67268f9e59a991f00eef1ff1fb9c8
git push --force-with-lease

@github-actions github-actions bot added the A3-backport Pull request is already reviewed well in another branch. label Dec 4, 2025
@github-actions github-actions bot requested a review from karolk91 December 4, 2025 08:49
Reverts #9842

Following on the discussion at
#10391, we don't want
to sort at decode level but rather to not require sorting at all among
the codebase

(cherry picked from commit 34034a9)
@karolk91 karolk91 force-pushed the backport-10459-to-stable2512 branch from f1c68a9 to a4bf05e Compare December 4, 2025 10:44
@karolk91 karolk91 marked this pull request as ready for review December 4, 2025 10:45
@karolk91 karolk91 requested a review from a team as a code owner December 4, 2025 10:45
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Dec 4, 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.

@karolk91 karolk91 added the R0-no-crate-publish-required The change does not require any crates to be re-published. label Dec 4, 2025
@karolk91 karolk91 enabled auto-merge (squash) December 4, 2025 12:56
@karolk91 karolk91 merged commit 6307083 into stable2512 Dec 4, 2025
248 of 253 checks passed
@karolk91 karolk91 deleted the backport-10459-to-stable2512 branch December 4, 2025 14:04
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