- Releases are taken from the branch
master
using tagsvX.X.X
- The
master
branch must refer to frontierparitytech/frontier/master
orpurestake/frontier/moonbeam-polkadot-vX.Y.Z
To release vX.Y.Z
:
- Create a PR with increment client version
- Get that PR approved and merged
- Tag master with
vX.Y.Z
and push to github - Start the github action "Publish Binary Draft" (on master branch)
- Review the generated Draft and clean a bit the messages if needed (keep it draft)
- Test the new client on internal tests networks (stagenet/moonsama/moonlama)
- Publish the client release draft
- When everything is ok, publish the new docker image: start github action Publish Docker with
vX.Y.Z
- Publish the new tracing image: on repo moonbeam-runtime-overrides, start github action
Publish Docker with
vX.Y.Z
and master - Documentation/Website/Tutorials have been updated
- Releases are taken from the branch
master
using tagsruntime-XXYY
- If the master branch contains changes that should not be included in the next runtime, then
create a
perm-runtime-XXYY
branch and create theruntime-XXYY
tag on that branch.
To release runtime-XXYY
:
- Create a PR that increment spec version (like #1051)
- Get that PR approved and merged
- Tag master with
runtime-XXYY
and push to github - Start the github action "Publish Runtime Draft"
- Review the generated Draft and clean a bit the messages if needed (keep it draft)
- Create the tracing runtime: start the github action "Create tracing runtime" on
purestake/moonbeam-runtime-overrides
- Upgrade runtime on our internal test network stagenet
- Ensure Type changes are reflected into PolkadotJs
- Test changes on stagenet
- Create new tracing image for partners: start the github action "Publish Docker"
on
purestake/moonbeam-runtime-overrides
- When everything is ok, publish the draft release
- Upgrade runtime on alphanet