AstarNetwork/Astar

Client & runtime split release process

Dinonard opened this issue · 0 comments

Description

Split the existing release process into two parts - client & runtime.
They should be independent.

  • split runtime & client release
  • client release would follow the existing vX.Y.Z semver notation
    • release would still be triggered via tag push same as today
    • only client is built, without runtimes
  • runtime release would follow new runtime-XXYY notation (where XX can be expanded)
    • new logic to handle tag & runtime release build
    • only 3 regular runtimes (+ 3 evm tracing runtimes) are built
    • all runtime spec versions would be the same (e.g. we can start with 1000)