Skip to content

Latest commit

 

History

History
18 lines (16 loc) · 903 Bytes

RELEASE.md

File metadata and controls

18 lines (16 loc) · 903 Bytes

Release

This document describes the process of releasing new versions of Tuist.

  1. Determine the new version:
    • Major if there's been a breaking change (+.0.0).
    • Minor by default (x.+.0).
    • Patch if it's a hotfix release (x.x.+).
    • Reach out to the core team if you have questions.
  2. Select the Tuist Release action in the GitHub Actions tab
  3. Select Run workflow
  4. Input the version from #1 into the action prompt and provide a title
  5. Run the workflow
  6. Wait for release workflow to finish
  7. Merge the PR created by the workflow
  8. Clone ProjectAutomation repository and run ./release.sh x.y.z
  9. Clone ProjectDescription repository and run ./release.sh x.y.z
  10. Once merged verify with tuist update