This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 378
Release Checklist for Runtime v9430 #2654
Labels
B0-silent
Changes should not be mentioned in any release notes
T9-release
This PR/Issue is related to topics touching the release notes.
Comments
EgorPopelyaev
added
B0-silent
Changes should not be mentioned in any release notes
T9-release
This PR/Issue is related to topics touching the release notes.
labels
May 30, 2023
Extrinsic ordering check ⬇️ |
bridge-hub-polkadot v9420 vs bridge-hub-polkadot v9430
Comparison of the following runtimes:
|
bridge-hub-kusama v9420 vs bridge-hub-kusama v9430
Comparison of the following runtimes:
|
bridge-hub-rococo v9420 vs bridge-hub-kusama v9430
Comparison of the following runtimes:
|
collectives v9420 vs collectives v9430
Comparison of the following runtimes:
|
contracts-rococo v9420 vs contracts-rococo v9430
Comparison of the following runtimes:
|
test-parachain v9420 vs test-parachain v9430
Comparison of the following runtimes:
|
statemine v9420 vs statemine v9430
Comparison of the following runtimes:
|
statemint v9420 vs statemint v9430
Comparison of the following runtimes:
|
westmint v9420 vs westmint v9430
Comparison of the following runtimes:
|
No |
All the integration tests pass. |
I've diffed all the Xcm and lib.rs for the relay chains and parachains. Nothing unexpected found. |
Backports from release 9430 to master: |
Release is out |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
B0-silent
Changes should not be mentioned in any release notes
T9-release
This PR/Issue is related to topics touching the release notes.
Release Checklist - Runtimes
All following checks must be completed before publishing a new release.
The release process is owned and led by @paritytech/release-engineering team.
The checks marked with 🦀 are meant to be checked by a runtime engineer.
Runtimes Release
Codebase
These checks should be performed on the codebase.
spec_version
has been incremented since thelast release for any native runtimes from any existing use on public (non-private/test) networks
SignedExtension
s have stayedthe same. Bump
transaction_version
otherwiseOn the release branch
The following checks can be performed after we have forked off to the release-candidate branch or started an additional release candidate branch (rc-2, rc-3, etc)
runtime state is correctly updated for any public (non-private/test)
networks
Github
notes
draft-release.
Post release
Read more about the release documentation.
The text was updated successfully, but these errors were encountered: