Bump polkadot-runtime-common from v0.9.14 to v0.9.15

[dependabot]

Bumps polkadot-runtime-common from v0.9.14 to v0.9.15.

Release notes

Sourced from polkadot-runtime-common's releases.

Polkadot v0.9.15

Upgrade Priority: Medium This release contains some runtime cleanup and migrations to prepare for the next runtime upgrade. It should be upgraded asap to prepare for the next runtime.

This is runtime only release and upgrading the nodes is not mandatory.

Native runtimes

• Polkadot: 9150
• Kusama: 9150
• Westend: 9150

This release was tested against the following versions of rustc. Other versions may work.

• rustc 1.57.0 (f1edd0429 2021-11-29)
• rustc 1.58.0-nightly (46b8e7488 2021-11-07)

WASM runtimes built with srtool v0.9.19 using rustc 1.57.0 (f1edd0429 2021-11-29).

Proposal hashes:

• polkadot_runtime-v9150.compact.compressed.wasm: 0x960d3ad3f42eb41ab2131e1561dd8cc20f87585e37d2d1b02525578204f11d4b
• kusama_runtime-v9150.compact.compressed.wasm: 0x0bc6607f0fc616102a4144621717d186f72b5864fd67879343461cf691a04c91

Runtime

• ⏳ pending non-critical audit Fix order of hook execution (Fix order of hook execution paritytech/substrate#10043)

Runtime migrations

• ⏳ pending non-critical audit Fix locked deposit of council voters (#4655)
• ⏳ pending non-critical audit Fix locked deposits of Nicks pallet (#4656)

Changelog

Sourced from polkadot-runtime-common's changelog.

Polkadot Release Process

Branches

• release-candidate branch: The branch used for staging of the next release. Named like release-v0.8.26

Notes

• The release-candidate branch must be made in the paritytech/polkadot repo in order for release automation to work correctly
• Any new pushes/merges to the release-candidate branch (for example, refs/heads/release-v0.8.26) will result in the rc index being bumped (e.g., v0.8.26-rc1 to v0.8.26-rc2) and new wasms built.

Release workflow

Below are the steps of the release workflow. Steps prefixed with NOACTION are automated and require no human action.

1. To initiate the release process:
2. branch master off to a release candidate branch:

• git checkout master; git pull; git checkout -b release-v0.8.26

2. In the substrate repo, check out the commit used by polkadot (this can be found using the following command in the polkadot repo: grep 'paritytech/substrate' Cargo.lock | grep -E '[0-9a-f]{40}' | sort | uniq
3. Branch off this substrate commit into its own branch: git branch -b polkadot-v0.8.26; git push origin refs/heads/polkadot-v0.8.26
4. In the polkadot repository, use diener to switch to this branch: diener update --branch "polkadot-v0.8.26" --substrate. Update Cargo.lock (to do this, you can run cargo build and then ctrl+c once it finishes fetching and begins compiling)
5. Push the polkadot release-v0.8.26 branch to Github: git push origin refs/heads/release-v0.8.26
6. NOACTION: The current HEAD of the release-candidate branch is tagged v0.8.26-rc1
7. NOACTION: A draft release and runtime WASMs are created for this release-candidate automatically. A link to the draft release will be linked in the internal polkadot matrix channel.
8. NOACTION: A new Github issue is created containing a checklist of manual steps to be completed before we are confident with the release. This will be linked in Matrix.
9. Complete the steps in the issue created in step 4, signing them off as completed
10. (optional) If a fix is required to the release-candidate:
11. Merge the fix with master first
12. Cherry-pick the commit from master to release-v0.8.26, fixing any merge conflicts. Try to avoid unnecessarily bumping crates.
13. Push the release-candidate branch to Github - this is now the new release- candidate
14. Depending on the cherry-picked changes, it may be necessary to perform some or all of the manual tests again.
15. If there are substrate changes required, these should be cherry-picked to the substrate polkadot-v0.8.26 branch and pushed, and the version of substrate used in polkadot updated using cargo update -p sp-io
16. Once happy with the release-candidate, tag the current top commit in the release candidate branch and push to Github: git tag -s -m 'v0.8.26' v0.8.26; git push --tags
17. NOACTION: The HEAD of the release branch will be tagged with v0.8.26, and a final draft release will be created on Github.

Security releases

... (truncated)

Commits

• 53dc81c Update deps
• ee075ed Fix build
• a632836 Remove some unused stuff
• 4530f66 Merge nicks PR #4656
• 351134d Merge council PR #4655
• dd8f4ce Deps update
• e18b4a4 bump spec version
• d573453 bump version to v0.9.15
• 6010438 Companion for #10324 - update frame-benchmarking/runtime-benchmarks (#4387)
• 94b1f8f companion for substrate/10377 (#4379)
• 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 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.