Skip to content

Manta Release Instructions

Jump to bottom
Shumo Chu edited this page May 26, 2021 · 1 revision

Version Semantics

A typical manta version would be like v<x>.<y>.<z>-<suffix>.

  • <x> major version: this is consistent with substrate code that the runtime code is based on
  • <y> mid version: this means major update or refactor of code compared with the substrate code that the runtime code is based on
  • <z> minor version: this will bump up each time for each release
  • <suffix> optional suffix: indicate the some special semantics of the release, for example alpha.4

Trigger Automatic Release Build

We use github action to trigger a release build. This can be done automatically but requires special instructions when merging PR that is a release PR. For example, if a PR, say, branch manta-release-tom-cruise is a release PR. After this PR passes code review and test. The committer need to do the following:

# suppose merge this PR to manta
git checkout manta
# merge the PR to manta, no-ff means squash history of the PR
git merge --no-ff manta-release-tom-cruise
# add a tag for release
git tag v3.0.0-alpha.4
# push the commit together with release tag to manta, this should trigger 
# a release build, and generate the release binary automatically 
git push origin manta --tags
Clone this wiki locally