This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Polkadot v0.9.13 Release checklist #4286
Comments
|
Tested the migrations. Polkadot only has #4080. Output: which is all good. Kusama has no migrations. Output: |
23 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Release Checklist
This is the release checklist for Polkadot v0.9.13. All following
checks should be completed before publishing a new release of the
Polkadot/Kusama/Westend runtime or client. The current release candidate can be
checked out with
git checkout release-v0.9.13Runtime Releases
These checks should be performed on the codebase prior to forking to a release-
candidate branch.
spec_versionhas been incremented since thelast release for any native runtimes from any existing use on public
(non-private/test) networks.
removed for any public (non-private/test) networks.
the same. Bump
transaction_versionif not.proxy filters.
runtime logic.
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.
runtime changes.
All Releases
without issue for 12 hours.
https://github.com/paritytech/polkadot/releases with relevant release
notes
draft-release
Notes
Burn In
Ensure that Parity DevOps has run the new release on Westend, Kusama, and
Polkadot validators for at least 12 hours prior to publishing the release.
Build Artifacts
Add any necessary assets to the release. They should include:
Release notes
The release notes should list:
based on the max priority of any client changes.
srtool
The release notes may also list:
regarding this release
Spec Version
A runtime upgrade must bump the spec number. This may follow a pattern with the
client release (e.g. runtime v12 corresponds to v0.8.12, even if the current
runtime is not v11).
Old Migrations Removed
Any previous
on_runtime_upgradefunctions from old upgrades must be removedto prevent them from executing a second time. The
on_runtime_upgradefunctioncan be found in
runtime/<runtime>/src/lib.rs.New Migrations
Ensure that any migrations that are required due to storage or logic changes
are included in the
on_runtime_upgradefunction of the appropriate pallets.Extrinsic Ordering
Offline signing libraries depend on a consistent ordering of call indices and
functions. Compare the metadata of the current and new runtimes and ensure that
the
module index, call indextuples map to the same set of functions. In caseof a breaking change, increase
transaction_version.To verify the order has not changed, you may manually start the following Github Action. It takes around a minute to run and will produce the report as artifact you need to manually check.
The things to look for in the output are lines like:
[Identity] idx 28 -> 25 (calls 15)- indicates the index forIdentityhas changed[+] Society, Recovery- indicates the new version includes 2 additional modules/pallets.[Identity] idx 25 (calls 15)Note: Adding new functions to the runtime does not constitute a breaking change
as long as the indexes did not change.
Proxy Filtering
The runtime contains proxy filters that map proxy types to allowable calls. If
the new runtime contains any new calls, verify that the proxy filters are up to
date to include them.
Benchmarks
There are three benchmarking machines reserved for updating the weights at
release-time. To initialise a benchmark run for each production runtime
(westend, kusama, polkadot):
be available to download as an artifact.
git patch patchfile.patchbig outliers (i.e., twice or half the weight).
Polkadot JS
Ensure that a release of Polkadot JS API contains any new types or
interfaces necessary to interact with the new runtime.
The text was updated successfully, but these errors were encountered: