This release contains the changes from polkadot-stable2506-4 to polkadot-stable2506-5.
ℹ️ Please note:
⚠️ This is a patch release for the stable version: stable2506 and contains only patches and fixes to the crates (list below).
The tag corresponding to the current patch release polkadot-stable2506-5 and matching the old pattern will be available under polkadot-v1.19.5.
The following crates were updated to the corresponding versions:
- sp-statement-store@21.2.0
- frame-system@41.0.2
- frame-executive@41.0.2
- sc-tracing@40.0.1
- pallet-revive@0.7.1
- sc-network-statement@0.33.2
- sc-statement-store@22.3.0
- polkadot-runtime-parachains@20.0.3
- cumulus-pallet-parachain-system@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.
[#9871]: trace_block: Support overwriting execute_block
This is required for example for parachains that require special extensions to be registered (e.g. ProofSizeExt) to succeed the block execution.
The node will make a best effort to detect whether its a parachain or not.
[#9965]: Limit the size of the statement for further gossiping
Limits the size of statements that are further gossiped over the network to prevent skipping oversized messages. The limit is set to match the network protocol's MAX_STATEMENT_NOTIFICATION_SIZE (1 MB), accounting for 1-byte vector length overhead because statements are sent as Vec<Statement>.
[#9912]: [WIP] Fix statement-store gossiping
Fixes gossiping and scalability issues in the statement-store networking: reduces traffic by propagating only recent statements, skips duplicate processing, and splits large batches to stay under MAX_STATEMENT_NOTIFICATION_SIZE.
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).)
[#10235]: offchain-worker: Do not intialize the entire System again
When calling offchain-worker we were initializing the entire System again with the same block we are running on top of. However, with the change to require strictly increasing block numbers the offchain-worker was failing. This is now solved by just registering the missing digests. The rest of the changes done by initialize are not important for offchain workers.
The pull request ensures that we are actually testing this behavior of the offchain worker now.
[#10180]: frame-system: Ensure that BlockNumber is strictly increasing
Otherwise a block should fail to build/import.
[#10149]: Ensure that multiple blocks in a PoV form a chain
validate_block ensures that all the blocks are connected to each other.
Rust compiler versions
This release was built and tested against the following versions of rustc.
Other versions may work.
- Rust Stable:
1.84.1