Conversation
|
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 |
|
This pull request is amending an existing release. Please proceed with extreme caution,
Emergency Bypass
If you really need to bypass this check: add |
|
All GitHub workflows were cancelled due to failure one of the required jobs. |
|
@Ank4n Hey Ankan, can we avoid a major bump of the |
|
@EgorPopelyaev should I make thee
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 |
|
@EgorPopelyaev I've added
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 |
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>
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>
Backport #10502 into
stable2512from Ank4n.NOTE: this PR introduces a breaking change in the signature of the extrinsic
set_staking_configsthat 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 putvalidate:falsein the related section of the prdoc around pallet-staking-async. Please note that only Root origin can callset_staking_configsso 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.