Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client & runtime split release process #1347

Closed
Dinonard opened this issue Aug 30, 2024 · 0 comments · Fixed by #1352
Closed

Client & runtime split release process #1347

Dinonard opened this issue Aug 30, 2024 · 0 comments · Fixed by #1352
Assignees
Labels
project Issue is part of an ongoing project

Comments

@Dinonard
Copy link
Member

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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
project Issue is part of an ongoing project
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant