2018-07-22 07:56:49 +08:00
|
|
|
# Release
|
|
|
|
|
|
2018-07-23 19:59:52 +08:00
|
|
|
This document describes the process of releasing new versions of tuist.
|
2018-07-22 07:56:49 +08:00
|
|
|
|
2021-09-15 02:34:49 +08:00
|
|
|
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:
|
2018-07-22 07:56:49 +08:00
|
|
|
|
|
|
|
|
- Major if there's been a breaking change.
|
|
|
|
|
- Minor by default.
|
|
|
|
|
- Patch if it's a hotfix release.
|
2021-09-15 02:34:49 +08:00
|
|
|
|
|
|
|
|
3. Update the version in the `Constants.swift` file.
|
|
|
|
|
4. Update the `CHANGELOG.md` to include the version section.
|
|
|
|
|
5. Commit the changes and tag the commit with the version `git tag x.y.z`.
|
2021-09-15 03:16:21 +08:00
|
|
|
6. Build tuist artifacts by running `./fourier release tuist x.y.z`.
|
|
|
|
|
7. 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.
|
|
|
|
|
8. Run `tuist update` and verify that the new version is installed and runs.
|
