Skip to content

Latest commit

 

History

History
19 lines (15 loc) · 1020 Bytes

RELEASE.md

File metadata and controls

19 lines (15 loc) · 1020 Bytes

Release

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

  1. First make sure you are in master and the latest changes are pulled: git pull origin master
  2. Ensure that the project is in a releasable state by running the tests: swift test and bundle exec rake features.
  3. 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. Package and upload the release to GCS by running bundle exec rake release.
  5. Upload the installation scripts to GCS by running bundle exec rake release_scripts.
  6. 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.
  7. Run tuist update and verify that the new version is installed and runs.