Bump sp-block-builder from polkadot-v1.9.0 to polkadot-v1.14.0

[dependabot]

Bumps sp-block-builder from polkadot-v1.9.0 to polkadot-v1.14.0.

Release notes

Sourced from sp-block-builder's releases.

Polkadot v1.14.0

This release contains the changes from polkadot-v1.13.0 to polkadot-v1.14.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.

#4724: Fix core sharing and make use of scheduling_lookahead during backing

Core sharing (two or more parachains scheduled on the same core with interlaced assignments) was not working correctly. Adds the neccessary fixes to the backing subsystems. Moreover, adds support for backing collations which are built and advertised ahead of time (with up to scheduling_lookahead relay chain blocks in advance).

#4833: Reinitialize should allow to override existing config in collationGeneration

The Reinitialize collationGeneration subsystem message currently fails if no other config is already set. As it is difficult to query the collationGeneration subsystem to check when to call Initialize or Reinitialize, this PR proposes that Reinitialize overrides the configuration regardless if there was one already set.

#4730: rpc upgrade jsonrpsee to v0.23.1

Upgrade the rpc library jsonrpsee to v0.23.1 to utilize:

• Add Extensions which we now is using to get the connection id (used by the rpc spec v2)
• Update hyper to v1.0, http v1.0, soketto and related crates (hyper::service::make_service_fn is removed)
• The subscription API for the client is modified to know why a subscription was closed.

#4618: Unify logic for fetching the :code of a block

Client::code_at will now use the same substitute to determine the code for a given block as it is done when executing any runtime call.

#4844: Make Verifier::verify and BlockImport::check_block use &self instead of &mut self

Verifier::verify and BlockImport::check_block were refactored to use &self instead of &mut self because there is no fundamental requirement for those operations to be exclusive in nature.

#4733: Add pov-recovery unit tests and support for elastic scaling

Adds unit tests for cumulus pov-recovery and support for elastic scaling (recovering multiple candidates in a single relay chain block).

Changelog for Runtime Dev

... (truncated)

Changelog

Sourced from sp-block-builder'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 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

• 3649614 Bump rococo-parachain spec_version
• 627a123 Reordering prdocs for the release 1.14.0
• 3163cee Bump spec_version to 1_014_000
• 4c3a026 Bump crate versions in: cumulus/polkadot-parachain/Cargo.toml
• 6a148a4 Bump node version to 1.14.0 in polkadot-cli
• 929a273 pallet assets: optional auto-increment for the asset ID (#4757)
• f1db2c6 Coretime: Add request revenue info (#3940)
• 4a7155e network: Upgrade litep2p to v0.6.2 (#4799)
• b4ae5b0 Fellowship-core: add fast promote (#4877)
• 7506956 [xcm] runtime api for LocationToAccount conversions (#4857)
• 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)