Skip to content

Latest commit

 

History

History
17 lines (13 loc) · 815 Bytes

RELEASE.md

File metadata and controls

17 lines (13 loc) · 815 Bytes
Raw

Release

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

  1. First make sure you are in main and the latest changes are pulled: git checkout main && git pull origin main
  2. Determine the new version:
  • Major if there's been a breaking change.
  • Minor by default.
  • Patch if it's a hotfix release.
  1. Update the version in the Constants.swift file.
  2. Update the CHANGELOG.md to include the version section.
  3. Commit the changes and tag the commit with the version git tag x.y.z.
  4. Build tuist artifacts by running ./fourier release tuist x.y.z.
  5. Create a release on GitHub with the version as a title, the body from the CHANGELOG file, and attach the artifacts in the build/ directory.
  6. Run tuist update and verify that the new version is installed and runs.