This release contains the changes from polkadot-stable2407-3 to polkadot-stable2407-4.
ℹ️ Please note:
⚠️ This is a patch release for the stable version: stable2407. If your nodes are already running on the latest stable version (stable2409 or stable2409-1), no upgrade or changes are necessary.
The tag corresponding to the current patch release polkadot-stable2407-4 and matching the old pattern will be available under polkadot-v1.15.4.
Also the deb package for this version will be attached here for the manual installation and published under the new distribution - stable2407. To install it via apt please extend the /etc/apt/sources.list.d/parity.list by:
echo 'deb [signed-by=/usr/share/keyrings/parity.gpg] https://releases.parity.io/deb stable2407 main' >> /etc/apt/sources.list.d/parity.listChangelog
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).)
[#6148]: Fix migrations for pallet-xcm
pallet-xcm stores some operational data that uses Versioned* XCM types. When we add a new XCM version (XV), we deprecate XV-2 and remove XV-3.
This PR extends the existing MigrateToLatestXcmVersion to include migration for the Queries, LockedFungibles, and RemoteLockedFungibles storage types.
Additionally, more checks were added to try_state for these types.
[#6068]: Add assets in pool with native to query_acceptable_payment_assets
The XcmPaymentApi::query_acceptable_payment_assets API can be used to get a list of all the assets that can be used for fee payment.
This is usually just the native asset, but the asset hubs have the asset conversion pallet.
In the case of the asset hubs, this list now includes all assets in a liquidity pool with the native one.
[#6205]: pallet-message-queue: Fix max message size calculation
The max size of a message should not depend on the weight left in a given execution context. Instead the max message size depends on the service weights configured for the pallet. A message that may does not fit into on_idle is not automatically overweight, because it may can be executed successfully in on_initialize or in another block in on_idle when there is more weight left.
[#4803]: Fix for issue
When the status of the queue is on_initialize, throw a defensive message and return weight of 0, however when status is on_idle, do not throw a defensive message, only return weight of 0
Changelog for Runtime User
ℹ️ These changes are relevant to: Anyone using the runtime. This can be a token holder or a dev writing a front end for a chain.
[#6004]: Remove redundant XCMs from dry run's forwarded xcms
The DryRunApi was returning the same message repeated multiple times in the forwarded_xcms field. This is no longer the case.
Rust compiler versions
This release was built and tested against the following versions of rustc.
Other versions may work.
- Rust Stable:
"1.81.0"
Docker images
The docker images for the polkadot node binary and the polkadot-parachain binary can be found at Docker hub (will be available a few minutes after the release has been published):
You may also pull it with:
docker pull parity/polkadot:stable2407-4
or
docker pull parity/polkadot-parachain:stable2407-4