Update to polkadot-sdk stable2506 and Rust 1.88#1302
Merged
tmpolaczyk merged 131 commits intomasterfrom Nov 3, 2025
Merged
Conversation
Contributor
WASM runtime size check:Compared to target branchdancebox runtime: 1848 KB (+156 KB) flashbox runtime: 1080 KB (+36 KB) dancelight runtime: 2592 KB (+76 KB) 🚨 starlight runtime: 2552 KB (+80 KB) 🚨 container chain template simple runtime: 1452 KB (+104 KB) container chain template frontier runtime: 1816 KB (+168 KB) |
evgeny-s
reviewed
Oct 27, 2025
evgeny-s
reviewed
Oct 27, 2025
Agusrodri
reviewed
Oct 28, 2025
Had to manually update the polkadot-sdk Cargo.lock to fix the build error
girazoki
reviewed
Oct 30, 2025
girazoki
reviewed
Oct 30, 2025
girazoki
reviewed
Oct 30, 2025
girazoki
reviewed
Oct 30, 2025
girazoki
approved these changes
Oct 30, 2025
ParthDesai
reviewed
Oct 30, 2025
evgeny-s
reviewed
Oct 30, 2025
Contributor
evgeny-s
left a comment
evgeny-s
left a comment
There was a problem hiding this comment.
@tmpolaczyk
We have a job that checks if we need to update runtime API-s.
We can enable it using the label: dependency-upgrade.
Do you want to include it?
Or run it manually
nanocryk
reviewed
Nov 3, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please also review the snowbridge changes in our polkadot-sdk fork: moondance-labs/polkadot-sdk#15
Notable changes:
libp2p can still be used by passing
--network-backend=libp2p.We include a few cherry-picks to fix litep2p issues, using litep2p 0.11.1. The official polkadot stable2506 release uses 0.9.5, so there may be some issues that affect polkadot relay chains but not tanssi. litep2p diff
This broke some of our tests, but it's something that should only happen in a local network when running multiple nodes in the same machine. See #1337
We were already using it almost everywhere so this is fine. I'm leaving the explicit tx-pool CLI args in zombienet tests for now, we can clean it up later.
We get a deprecation warning so we removed it from our pallets. But parity decided to allow(deprecated) so we still must include it for parity pallets.
To improve bootnode discoverability, doesn't affect us much because we use the data preservers pallet. Moved to a separate PR for easier review: #1344
Anti-DOS feature, we don't care.
TrieCacheContextarg. Onchain => Trusted, Offchain => Untrusted.This is an optimization to promise that the cache size is bounded, we only use
Untrustedin our codebase, copied from thestate_atimpl from cumulus.type RelayParentOffset: Allow building on older relay parents paritytech/polkadot-sdk#8299Allows collators to build blocks using an older relay block. Disabled now (set to 0). It allows to reduce forks on the parachain side, but it increases the delay for processing XCM messages.
relay_parent_descendants.This is related to the
RelayParentOffset. We didn't enable that feature so this should simply be a refactor. I fixed some small discrepancies between our collator and upstream, and created a ticket to fix some more (MD-1403).