11# Releasing New Rez Versions
22
3- To merge a PR to master and release a new version:
3+ To merge a PR to the ` main ` branch and release a new version:
44
551 . Merge the PR locally, following the instructions given on GitHub in the
6- ` command line instructions ` link (but do not push to master yet);
6+ ` command line instructions ` link (but do not push to ` main ` yet);
772 . Run the tests (rez-selftest) to double check nothing is broken;
8- 3 . Make sure the [ rez version] ( https://github.com/AcademySoftwareFoundation/rez/blob/master /src/rez/utils/_version.py )
8+ 3 . Make sure the [ rez version] ( https://github.com/AcademySoftwareFoundation/rez/blob/main /src/rez/utils/_version.py )
99 is correct, and change if necessary. The version may have been correct at the
1010 time of PR submission, but may need an update due to releases that have occurred
1111 since;
@@ -17,10 +17,10 @@ To merge a PR to master and release a new version:
1717 ```
1818 This command prints the changelog entry to stdout, which you can then paste in
1919 to the top of CHANGELOG.md.
20- 5 . Commit and push to master ;
20+ 5 . Commit and push to ` main ` ;
21216 . Wait for all Github workflows to pass;
22227 . Run the release-rez utility script. This performs the following actions:
23- * Creates tag on latest version, and pushes tag to master ;
23+ * Creates tag on latest version, and pushes tag to ` main ` ;
2424 * Generates the new GitHub release (https://github.com/AcademySoftwareFoundation/rez/releases ).
2525 ```
2626 ]$ python ./release-rez.py
0 commit comments