Bump sc-cli from polkadot-v1.9.0 to polkadot-v1.12.0

[dependabot]

Bumps sc-cli from polkadot-v1.9.0 to polkadot-v1.12.0.

Release notes

Sourced from sc-cli's releases.

Polkadot v1.12.0

This release contains the changes from polkadot-v1.11.0 to polkadot-v1.12.0.

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.

#4442: Improve mock relay in --dev mode to support async backing

Support async backing in --dev mode. Improve the relay mock MockValidationDataInherentDataProvider to mach expectations of async backing runtimes.

#4185: State trie migration on asset-hub westend and collectives westend

On westend and rococo asset-hub and collectives westend the state version is switched to one and a manual migration will be operate as describe in https://hackmd.io/JagpUd8tTjuKf9HQtpvHIQ 2.2 Running the signed migration with account 5F4EbSkZz18X36xhbsjvDNs6NuZ82HyYtq5UiJ1h9SBHJXZD.

#4157: Bridge: added free headers submission support to the substrate-relay

Bridge finality and parachains relayer now supports mode, where it only submits some headers for free. There's a setting in a runtime configuration, which introduces this "free header" concept. Submitting such header is considered a common good deed, so it is free for relayers.

#4457: sc-service: export all public functions

A PR #3166 converted private functions used in spawn_tasks() to public to make it possible to have custom implementation of the spawn_tasks(). However, not all functions were included in the list of exports from sc-service crate.

#4211: Re-prepare PVF artifacts only if needed

When a change in the executor environment parameters can not affect the prepared artifact, it is preserved without recompilation and used for future executions. That mitigates situations where every unrelated executor parameter change resulted in re-preparing every artifact on every validator, causing a significant finality lag.

#3962: Change fork calculation algorithm.

This PR changes the fork calculation and pruning algorithm to enable future block header pruning. During the finalization of the block we prune known stale forks, so forks are pruned faster.

... (truncated)

Changelog

Sourced from sc-cli's changelog.

Release

The outputs of a release are the polkadot and polkadot-parachain node binaries, the runtimes for Westend & Rococo and their system parachains, and new crate versions published to crates.io.

Setup

We have two branches: master and stable. master is the main development branch where normal Pull Requests are opened. Developers need to mostly only care about this branch.
The stable branch contains a version of the code that is ready to be released. Its contents are always audited. Merging to it is restricted to Backports.

Versioning

We are releasing multiple different things from this repository in one release, but we don't want to use the same version for everything. Thus, in the following we explain the versioning story for the crates, node and Westend & Rococo. To easily refer to a release, it shall be named by its date in the form stableYYMMDD.

Crate

We try to follow SemVer 2.0.0 as best as possible for versioning our crates. The definitions of major, minor and patch version for Rust crates are slightly altered from their standard for pre 1.0.0 versions. Quoting rust-lang.org:

Initial development releases starting with “0.y.z” can treat changes in “y” as a major release, and “z” as a minor release. “0.0.z” releases are always major changes. This is because Cargo uses the convention that only changes in the left-most non-zero component are considered incompatible.

SemVer requires a piece of software to first declare a public API. The public API of the Polkadot SDK is hereby declared as the sum of all crates' public APIs.

Inductively, the public API of our library crates is declared as all public items that are neither:

• Inside a __private module
• Documented as "unstable" or "experimental" in the first line of docs
• Bear unstable or experimental in their absolute path

Node

The versioning of the Polkadot node is done most of the time by only incrementing the minor version. The major version is only bumped for special releases and the patch can be used for an out of band release that fixes some critical bug. The node version is not following SemVer. This means that the version doesn't express if there are any breaking changes in the CLI interface or similar. The node version is declared in the NODE_VERSION variable.

Westend & Rococo

For the these networks, in addition to incrementing the Cargo.toml version we also increment the spec_version and sometimes the transaction_version. The spec version is also following the node version. Its schema is: M_mmm_ppp and for example 1_002_000 is the node release 1.2.0. This versioning has no further meaning, and is only done to map

... (truncated)

Commits

• b401690 Bump transaction_version rococo and westend
• 3b6dcfe fix flow due to renaming of the srtool.yml
• 21c5d3d Bump spec_version rococo-parachain
• 05cccf2 Reordering prdocs for the release 1.12.0
• 8eb88a1 Bump spec_version to 1_012_000
• a084e48 Bump crate versions in: cumulus/polkadot-parachain/Cargo.toml
• 822de02 Bump node version to 1.12.0 in polkadot-cli
• 59d7e03 Export all public functions of sc-service (#4457)
• 404027e Fix extrinsics count logging in frame-system (#4461)
• f2b367e Add OnFinality kusama bootnode (#4458)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #26.