This release contains the changes from polkadot-stable2506-2 to polkadot-stable2506-3.
ℹ️ Please note:
⚠️ This is a patch release for the stable version: stable2506 and contains only patches and fixes to the crates (list below). No binary or docker images will be provided for this release.
The tag corresponding to the current patch release polkadot-stable2506-3 and matching the old pattern will be available under polkadot-v1.19.3.
The following crates were updated to the corresponding versions:
- sp-statement-store@21.1.0
- sc-statement-store@22.1.0
- pallet-ranked-collective@41.0.1
- cumulus-pallet-xcmp-queue@0.21.1
Changelog
Changelog for Node Dev
ℹ️ These changes are relevant to: Those who build around the client side code. Alternative client builders, SMOLDOT, those who consume RPCs. These are people who are oblivious to the runtime changes. They only care about the meta-protocol, not the protocol itself.
[#9868]: Fix the deadlock during statements gossiping
During high load the statement store experiences deadlock-like behavior: every second statements were gossiping, locking the index which possibly caused the deadlock. After the fix, the observed behavior no longer occurs.
Changelog for Runtime Dev
ℹ️ These changes are relevant to: All of those who rely on the runtime. A parachain team that is using a pallet. A DApp that is using a pallet. These are people who care about the protocol (WASM, not the meta-protocol (client).)
[#9836]: Add remove_by method to statement store runtime interface
The runtime interface for the statement store and the extensions have a new method remove_by that allows removing all statements made by one account. This is useful for cleaning up statements after the allowance given to an account has been revoked.
The actual rust semver is major but we consider the rust semantic experimental until we use it in production.
[#9781]: Limit the number of signals per XCMP page
Right now we have only 2 XCMP signals: SuspendChannel and ResumeChannel and we can write at most 1 per page.
Let's also add a limit when reading the signals in a page. Even if now 1 is enough, since in the future we might add more signals, let's have a limit of 3 per page.
[#9641]: Account for PoV size when enqueing XCMP message
Related to #9630 , but adjusting the benchmark
Using #[benchmark(pov_mode = Measured)] for the enqueue_empty_xcmp_message_at benchmark.
[#9731]: simulate rank_to_votes conversion in vote benchmark
Fixes benchmarking failures for the vote extrinsic in pallet-ranked-collective by properly simulating the rank_to_votes conversion process. Previously used hardcoded vote values which caused assertion failures when using custom VoteWeight converters (e.g., in
Ambassador Collective configuration). The fix calculates vote weight based on member's actual rank and minimum required rank for the class.
Rust compiler versions
This release was built and tested against the following versions of rustc.
Other versions may work.
- Rust Stable:
1.84.1