834 B
834 B
Release
This document describes the process of releasing new versions of tuist.
- First make sure you are in master and the latest changes are pulled:
git pull origin master
- Ensure that the project is in a releaseable state by running the tests:
swift test
. - Determine the new version:
- Major if there's been a breaking change.
- Minor by default.
- Patch if it's a hotfix release.
- Update the version in the
Constants.swift
file. - Update the
CHANGELOG.md
to include the version section. - Generate the documentation with
jazzy
. - Commit the changes and tag the commit with the version
git tag x.y.z
. - Package the release running
make package-release
. - Push the changes to remote and create a new release on GitHub including the changelog. Attach all the files in the
build/
directory.