Release Checklist for Runtime v1.0.0-epo

[github-actions]

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.

• the spec_version has been incremented since the
  last release for any native runtimes from any existing use on public (non-private/test) networks
• 🦀 previously completed migrations are removed for any public (non-private/test) networks
• pallet and extrinsic ordering as well as SignedExtensions have stayed
  the same. Bump transaction_version otherwise
• the benchmarks ran
• the weights have been updated for any modified runtime logic
• 🦀 the new weights are sane, there are no significant (>50%) drops or rises with no reason
• 🦀 XCM config is compatible with the configurations and versions of relevant interlocutors, like the Relay Chain.

On 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)

• Verify new migrations complete successfully, and the
  runtime state is correctly updated for any public (non-private/test)
  networks
• Run integration tests, and make sure they pass.
• Push runtime upgrade to Asset Hub Westend and verify network stability
• Push runtime upgrade to Collectives and verify network stability
• Push runtime upgrade to Bridge-Hub-Kusama and verify network stability

Github

• Check that a draft release has been created at the Github Releases page with relevant release
  notes
• Check that build artifacts have been added to the
  draft-release.

Post release

• 🦀 all commits (runtime version bumps, fixes) on this release branch have been merged back to master.

---

Read more about the release documentation.