Polkadot SDK stable2609-2 hardens XCM rollback and bounds Revive receipts; seven break APIs
Parity has published polkadot-stable2609-2, a patch release for the stable2609 branch of the Polkadot SDK. According to the release page on GitHub, it contains only patches and fixes to crates, with no binaries or Docker images, and will also carry the tag polkadot-v1.25.2. Seven of the changes count as breaking under Rust semantic versioning, each bumping the major version of at least one crate.
The XCM work is described in most detail. Pull request 13704 adds more rollback hardening to the XCM executor. The release notes stress that none of the fixes address vulnerabilities, but say they could become relevant if assumptions upstream or downstream of the executor change, so the PR adds defence in depth and documents the remaining assumptions. Concretely, delivery fees for report instructions and failed BuyExecution state are rolled back, the asset used for delivery fees is recorded only when BuyExecution succeeds, ExportMessage fails when the exporter cannot deliver, and the remaining storage-changing instructions run transactionally.
On the smart contract side, pallet-revive now bounds the size of the receipt produced per transaction. A new storage value tracks committed receipt logs only while an Ethereum transaction or its dry run is executing, and a new error, ReceiptTooLarge, takes index 0x45, leaving 0x44 unused to match later releases. The notes say no storage migration or configuration change is needed, but code that matches errors exhaustively needs a new arm. A second Revive change aligns the terminate precompile with the corresponding opcodes.
Other breaking entries touch governance and assets: pallet-bounties now pays out only spendable funds, pallet-psm rejects the None origin as an admin and simplifies its account handling, the multi-block election provider fixes the signed base deposit at registration, and pallet-nfts and pallet-uniques enforce a full deposit transfer when a collection changes owner.

Why it matters
For parachain teams on stable2609, this is a dependency update with compile-time consequences rather than a node upgrade. The XCM changes, in the release notes' own words, reduce the number of assumptions the executor relies on, before any of them can turn into a vulnerability.