Bump polkadot-runtime-common from polkadot-v1.7.1 to polkadot-v1.8.0

[dependabot]

Bumps polkadot-runtime-common from polkadot-v1.7.1 to polkadot-v1.8.0.

Release notes

Sourced from polkadot-runtime-common's releases.

Polkadot v1.8.0

This release contains the changes from polkadot-v1.7.2 to polkadot-v1.8.0.

Changelog

Changelog for Node Dev

#3395: benchmarking-cli pallet subcommand: refactor --list and add --all option

pallet subcommand's --list now accepts two values: "all" and "pallets". The former will list all available benchmarks, the latter will list only pallets. Also adds --all to run all the available benchmarks and --no-csv-header to omit the csv-style header in the output. NOTE: changes are backward compatible.

#3079: Implement transaction_unstable_broadcast and transaction_unstable_stop

A new RPC class is added to handle transactions. The transaction_unstable_broadcast broadcasts the provided transaction to the peers of the node, until the transaction_unstable_stop is called. The APIs are marked as unstable and subject to change in the future. To know if the transaction was added to the chain, users can decode the bodies of announced finalized blocks. This is a low-level approach for transactionWatch_unstable_submitAndWatch.

#3160: prospective-parachains: allow requesting a chain of backable candidates

Enable requesting a chain of multiple backable candidates. Will be used by the provisioner to build paras inherent data for elastic scaling.

#3244: Make the benchmark pallet command only require a Hasher

Currently the benchmark pallet command requires a Block type, while only using its hasher. Now this is changed to only require the Easher. This means to use HashingFor<Block> in the place where Block was required. Example patch for your node with cmd being BenchmarkCmd::Pallet(cmd):

- cmd.run::<Block, ()>(config)
+ cmd.run::<HashingFor<Block>, ()>(config)

#3308: Parachains-Aura: Only produce once per slot

With the introduction of asynchronous backing the relay chain allows parachain to include blocks every 6 seconds. The Cumulus Aura implementations, besides the lookahead collator, are building blocks when there is a free slot for the parachain in the relay chain. Most parachains are still running with a 12s slot duration and not allowing to build multiple blocks per slot. But, the block production logic will be triggered every 6s, resulting in error logs like: "no space left for the block in the unincluded segment". This is solved by ensuring that we don't build multiple blocks per slot.

#3166: Expose internal functions used by spawn_tasks

This allows to build a custom version of spawn_tasks with less copy-paste required

Changelog for Node Operator

#3358: Do not stall finality on spam disputes

This PR fixes the issue that periodically caused finality stalls on Kusama due to disputes happening there in combination with disputes spam protection mechanism. See: paritytech/polkadot-sdk#3345

#3301: rpc server add rate limiting.

Add rate limiting for RPC server which can be utilized by the CLI --rpc-rate-limit <calls per minute>

... (truncated)

Changelog

Sourced from polkadot-runtime-common'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. 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 from an on chain spec_version easily to the release in this repository.
The Westend testnet will be updated to a new runtime every two weeks with the latest nightly release.

Backports

From master to stable

... (truncated)

Commits

• ec7817e adjust release notifications GHA
• 203fb45 Move prdoc files to the release folder
• cd94c57 Merge branch 'release-polkadot-v1.8.0' of https://github.com/paritytech/polka...
• 93e5099 Fix multiple cores 1.8 (#3477)
• 0053646 Contracts Add new version for marking new stable API (#3415)
• aaa98ea Add more debug logs to understand if statement-distribution misbehaving (#3476)
• 9b6d331 Move prdoc file to the release folder
• 43b7542 sc-consensus-beefy: pump gossip engine while waiting for initialization condi...
• 815d767 Bump spec_version
• 2631791 Add matrix public channels for release announcements (#3430)
• 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]

Looks like polkadot-runtime-common is up-to-date now, so this is no longer needed.