-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Polkadot v0.9.39 Release checklist #6781
Comments
extrinsic check fails on rococo due to outdated polkadot-js-tools: latest: Pulling from jacogr/polkadot-js-tools |
Metadata comparison:
|
Metadata comparison:
|
Metadata comparison:
|
going to sync txver with previous release |
rc2 ^ |
westend upgrade https://github.com/paritytech/devops/issues/2388 |
published |
Release Checklist
This is the release checklist for Polkadot v0.9.39. All following
checks should be completed before publishing a new release of the
Polkadot/Kusama/Westend/Rococo runtime or client. The current release candidate can be
checked out with
git checkout release-v0.9.39
Runtime Releases
These checks should be performed on the codebase prior to forking to a release-
candidate branch.
spec_version
has been incremented since thelast release for any native runtimes from any existing use on public
(non-private) networks. If the runtime was published (release or pre-release), either
the
spec_version
orimpl
must be bumped. -> 7e5afe4removed for any public (non-private/test) networks. -> no migrations
the same. Bump
transaction_version
if not. -> https://github.com/paritytech/polkadot/actions/runs/4283269757Verify new extrinsics have been correctly whitelisted/blacklisted forto be removedproxy filters.
runtime logic. -> bf2ebf3
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)
Verify new migrations complete successfully, and the-> cc @s3krit (there is CI for this too now)runtime state is correctly updated for any public (non-private/test)
networks.
Verify Polkadot JS API are up to date with the latest-> cc @s3kritruntime changes.
All Releases
Check that the new client versions have run on the network-> cc @s3kritwithout issue for 12+ hours on >75% of our validator nodes.
https://github.com/paritytech/polkadot/releases with relevant release
notes
draft-release
freenotes
were added into the release branch after the latest generated RCThe text was updated successfully, but these errors were encountered: