Skip to content

[stable2512] Backport #10502#10810

Merged
sigurpol merged 11 commits intostable2512from
backport-10502-to-stable2512
Jan 20, 2026
Merged

[stable2512] Backport #10502#10810
sigurpol merged 11 commits intostable2512from
backport-10502-to-stable2512

Conversation

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

@paritytech-release-backport-bot paritytech-release-backport-bot bot commented Jan 14, 2026

Backport #10502 into stable2512 from Ank4n.

NOTE: this PR introduces a breaking change in the signature of the extrinsic set_staking_configs that now has a new extra input parameter: are_nominators_slashable. This is needed to be able to deliver the feature of having non slashable nominator past March 14th. Because of that, we have put validate:false in the related section of the prdoc around pallet-staking-async. Please note that only Root origin can call set_staking_configs so the practical impact of the breaking change is basically zero. We need a Governance referendum to tune the parameters and set nominators as non slashable around March 14th so we need OpenGov to actually use the new version to be able to deliver the requested feature, we can't really avoid that. Adding an extra extrinsic just to avoid the breaking change seems an unnecessary overkill.

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

@github-actions github-actions bot added the A3-backport Pull request is already reviewed well in another branch. label Jan 14, 2026
@github-actions github-actions bot requested a review from Ank4n January 14, 2026 22:20
@Ank4n Ank4n marked this pull request as ready for review January 19, 2026 10:48
@Ank4n Ank4n requested a review from a team as a code owner January 19, 2026 10:48
@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.

@paritytech-workflow-stopper
Copy link
Copy Markdown

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

@EgorPopelyaev
Copy link
Copy Markdown
Contributor

@Ank4n Hey Ankan, can we avoid a major bump of the pallet-staking-async?

@Ank4n
Copy link
Copy Markdown
Contributor

Ank4n commented Jan 19, 2026

@Ank4n Hey Ankan, can we avoid a major bump of the pallet-staking-async?

There are new storage and config constants, but we are not really breaking anything. I think that qualifies for minor?
cc: @sigurpol

Updated prdoc.

@Ank4n
Copy link
Copy Markdown
Contributor

Ank4n commented Jan 20, 2026

@EgorPopelyaev should I make thee

@Ank4n Hey Ankan, can we avoid a major bump of the pallet-staking-async?

It still complaining about adding this field in extrinsic signature, which unfortunately we can't get rid of and is a breaking change. But we need this in 2512 since we have a deadline to get this live by 14th March.

What do you suggest we do?

cc: @sigurpol

@sigurpol
Copy link
Copy Markdown
Contributor

sigurpol commented Jan 20, 2026

@EgorPopelyaev I've added validate: false for pallet-staking-async following:

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.

Is it acceptable ? We are fine in creating a new major version of staking-async crate. This change NEEDS to go live on chain before March 14th.

The breaking change is in the change of signature of the extrinsic set_staking_configs that now adds a new extra input parameter: are_nominators_slashable. Please note that only Root origin can call it so the practical impact of the breaking change is basically zero. We need a Governance referendum to tune the parameters and set nominators as non slashable by March 14th so we need OpenGov to actually use the new version to be able to deliver the requested feature, we can't really avoid that. Adding an extra extrinsic just to avoid the breaking change seems an unnecessary overkill.

@sigurpol sigurpol merged commit 229af71 into stable2512 Jan 20, 2026
248 of 254 checks passed
@sigurpol sigurpol deleted the backport-10502-to-stable2512 branch January 20, 2026 10:07
sigurpol added a commit that referenced this pull request Feb 11, 2026
Leftover from #10810 backport. The function was replaced by
prune_era_single_entry_cleanups in #10502.
sigurpol added a commit that referenced this pull request Feb 11, 2026
Leftover from #10810 backport. The function was replaced by
prune_era_single_entry_cleanups in #10502.

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
arturgontijo pushed a commit to moonbeam-foundation/polkadot-sdk that referenced this pull request Apr 1, 2026
Backport paritytech#10502 into `stable2512` from Ank4n.

NOTE: this PR introduces a breaking change in the signature of the
extrinsic `set_staking_configs` that now has a new extra input
parameter: `are_nominators_slashable`. This is needed to be able to
deliver the feature of having non slashable nominator past March 14th.
Because of that, we have put `validate:false` in the related section of
the prdoc around pallet-staking-async. Please note that only Root origin
can call `set_staking_configs` so the practical impact of the breaking
change is basically zero. We need a Governance referendum to tune the
parameters and set nominators as non slashable around March 14th so we
need OpenGov to actually use the new version to be able to deliver the
requested feature, we can't really avoid that. Adding an extra extrinsic
just to avoid the breaking change seems an unnecessary overkill.

See the
[documentation](https://github.com/paritytech/polkadot-sdk/blob/master/docs/BACKPORT.md)
on how to use this bot.

<!--
  # To be used by other automation, do not modify:
  original-pr-number: #${pull_number}
-->

---------

Co-authored-by: Ankan <10196091+Ank4n@users.noreply.github.com>
Co-authored-by: Ankan <ankan.anurag@gmail.com>
Co-authored-by: Egor_P <egor@parity.io>
Co-authored-by: Paolo La Camera <paolo@parity.io>
arturgontijo pushed a commit to moonbeam-foundation/polkadot-sdk that referenced this pull request Apr 1, 2026
Leftover from paritytech#10810 backport. The function was replaced by
prune_era_single_entry_cleanups in paritytech#10502.

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

3 participants