chore(deps): bump Polkadot SDK to stable2606 - #350
Open
bkontur wants to merge 3 commits into
Open
Conversation
Moves every SDK crate in `[workspace.dependencies]` from the `polkadot-stable2603` line to `polkadot-stable2606` (umbrella `polkadot-sdk 2606.0.0`) and pins `POLKADOT_SDK_VERSION` in `.github/env` so CI downloads the matching binaries. API adaptations required by the new release: - `sp-core` dropped its deprecated `sp_crypto_hashing` re-export, so `blake2_256`/`blake2_128`/`twox_128` now come from the `sp-crypto-hashing` crate directly. - `pallet_revive::Config` gained `Deposit` (PGAS-backed storage deposits) and `AutoMap`. Both runtimes keep the previous behaviour: native-currency deposits and an explicit `map_account` dispatchable. - `EthExtra` splits `Extension` into `ExtensionV0` plus `ExtensionOtherVersions` (Extrinsic Horizon); no other extrinsic versions are supported, hence `InvalidVersion`. - `cumulus_pallet_parachain_system::Config` gained `SchedulingSignatureVerifier`, left as `()` because V3 scheduling stalls a parachain whose collators and relay chain do not support it. - `RelayParentOffsetApi` is now at version 2 with `max_claim_queue_offset`, and the new `SchedulingV3EnabledApi` is implemented alongside it.
`polkadot-stable2606` bumps the in-code storage version of `cumulus-pallet-parachain-system` (v2 -> v3, which kills `PoVMessagesTracker`) and `cumulus-pallet-xcmp-queue` (v6 -> v7), so `try-runtime on-runtime-upgrade` against a previewnet snapshot failed with a version mismatch for both pallets plus corrupted-state reads in the parachain-system prefix. Schedules the SDK migrations for both. Each is gated on the on-chain version, so they stay no-ops once applied and are safe to leave in the tuple. The local runtime is unaffected: it sets `SingleBlockMigrations = ()` and has no live endpoint in `scripts/runtimes-matrix.json`.
bkontur
marked this pull request as ready for review
August 14, 2026 13:39
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
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.
Moves every SDK crate in
[workspace.dependencies]from thepolkadot-stable2603line topolkadot-stable2606(umbrellapolkadot-sdk 2606.0.0, node version 1.24.0) and pinsPOLKADOT_SDK_VERSIONin.github/envso CI downloads the matching binaries.API adaptations
sp-coredropped its deprecatedsp_crypto_hashingre-exportblake2_256/blake2_128/twox_128now come from thesp-crypto-hashingcrate directly (new workspace dependency, wired into 6 crates withstdpropagation)pallet_revive::ConfiggainedDeposit(PGAS-backed storage deposits, #11847) andAutoMap(#12135)Deposit = ()(native currency) andAutoMap = ConstBool<false>(the explicitmap_accountdispatchable stays enabled, which the PAPI SDK relies on)EthExtrasplitsExtensionintoExtensionV0+ExtensionOtherVersions(Extrinsic Horizon)ExtensionV0 = TxExtension,ExtensionOtherVersions = InvalidVersion— no other extrinsic versions are supportedcumulus_pallet_parachain_system::ConfiggainedSchedulingSignatureVerifier(); per the SDK docs, enabling V3 scheduling before collators and the relay chain support it stalls the parachainRelayParentOffsetApiis now version 2, andSchedulingV3EnabledApiis newmax_claim_queue_offset()delegates tocumulus_pallet_parachain_system::Pallet, andscheduling_v3_enabled()reports the verifier'sV3_SCHEDULING_ENABLED— same shape asasset-hub-westendat this tagNo usage of the APIs removed in this release (
pallet-transaction-payment'sCurrencyAdapter,parachains_common::AssetsToBlockAuthor).Storage migrations
2606 bumps the in-code storage version of two pallets we use, so the Paseo runtime schedules the SDK migrations for both:
Without them
try-runtime on-runtime-upgradefailed on a previewnet snapshot with a version mismatch for both pallets plus corrupted-state reads in the parachain-system prefix. Each migration is gated on the on-chain version, so both stay no-ops once applied and are safe to leave in the tuple. The local runtime is unaffected — it setsSingleBlockMigrations = ()and has no live endpoint inscripts/runtimes-matrix.json.Verification
Run locally (the usual remote build box was unreachable), all green:
cargo check --workspace --all-targetscargo build -p storage-parachain-runtime -p storage-paseo-runtime— both runtimes build forwasm32v1-none, so theno_stdpath is coveredcargo +nightly fmt --all,taplo format,zepter run,hawkeye format(both license configs)cargo clippy --all-targets --workspace -- -D warningsandcargo clippy --all-targets --all-features --workspace -- -D warningscargo test --workspace— 750 passed, 0 failed, 8 ignoredtry-runtime on-runtime-upgrade --checks=allagainst a freshwss://previewnet.substrate.dev/web3-storagesnapshot — exit 0, no errors,✅ Entire runtime state decodes without error, every pallet's try-state checks runNote for local runs:
--all-featurespulls inpallet-revive-fixtures, whose build script needssolconPATH(the CI image has it;SKIP_PALLET_REVIVE_FIXTURES=1works around it locally).Follow-up, not in this PR
The checked-in chain metadata —
crates/storage-subxt/metadata/storage_paseo_runtime.scaleandpackages/papi/.papi/metadata/parachain.scale— was generated against a 2603 runtime. Metadata changes with this bump (newpallet_reviveitems, the extrinsic-version rework), sojust subxt-codegen/papi generateshould be re-run against a 2606 node before the demos and integration tests are trusted.🤖 Generated with Claude Code