dnrops
/
tuist
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update the RELEASE process

This commit is contained in:
Pedro Piñera 2020-03-31 16:44:27 +02:00
parent e4c6da6773
commit 8baa605dd5
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
RELEASE.md
View File

@ -13,7 +13,8 @@ This document describes the process of releasing new versions of tuist.
4. Update the version in the `Constants.swift` file. 4. Update the version in the `Constants.swift` file.
5. Update the `CHANGELOG.md` to include the version section. 5. Update the `CHANGELOG.md` to include the version section.
6. Commit the changes and tag the commit with the version `git tag x.y.z`. 6. Commit the changes and tag the commit with the version `git tag x.y.z`.
7. Package and upload the release to GCS by running `bundle exec rake release`. 7. Select the Xcode version 11.3.1 before building the binaries: `sudo xcode-select -s /Applications/Xcode_11.3.1.app`.
8. Upload the installation scripts to GCS by running `bundle exec rake release_scripts`. 8. Package and upload the release to GCS by running `bundle exec rake release`.
9. 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. 9. Upload the installation scripts to GCS by running `bundle exec rake release_scripts`.
10. Run `tuist update` and verify that the new version is installed and runs. 10. 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.
11. Run `tuist update` and verify that the new version is installed and runs.