@@ -13,13 +13,9 @@ the maintenance branch. If so, release a last patch release first. See
1313- Check the result of ` git diff vX.Y-1.Z' ChangeLog ` . (For example:
1414 ` git diff v2.3.4 ChangeLog ` )
1515- Install the release dependencies: ` pip3 install -r requirements_test.txt `
16- - Bump the version and release by using ` tbump X.Y.0 --no-push ` . (For example:
17- ` tbump 2.4.0 --no-push ` )
18- - Check the result visually and then by triggering the "release tests" workflow in
19- GitHub Actions first.
20- - Push the tag.
21- - Release the version on GitHub with the same name as the tag and copy and paste the
22- appropriate changelog in the description. This triggers the PyPI release.
16+ - Bump the version and release by using ` tbump X.Y.0 --no-push --no-tag ` . (For example:
17+ ` tbump 2.4.0 --no-push --no-tag ` )
18+ - Check the commit created with ` git show ` amend the commit if required.
2319- Move the ` main ` branch up to a dev version with ` tbump ` :
2420
2521``` bash
@@ -34,8 +30,15 @@ tbump 2.5.0-dev0 --no-tag --no-push
3430git commit -am " Upgrade the version to 2.5.0-dev0 following 2.4.0 release"
3531```
3632
37- Check the result and then upgrade the main branch
33+ Check the commit and then push to a release branch
3834
35+ - Open a merge request with the two commits (no one can push directly on ` main ` )
36+ - Trigger the "release tests" workflow in GitHub Actions.
37+ - After the merge, recover the merged commits on ` main ` and tag the first one (the
38+ version should be ` X.Y.Z ` ) as ` vX.Y.Z ` (For example: ` v2.4.0 ` )
39+ - Push the tag.
40+ - Release the version on GitHub with the same name as the tag and copy and paste the
41+ appropriate changelog in the description. This triggers the PyPI release.
3942- Delete the ` maintenance/X.Y-1.x ` branch. (For example: ` maintenance/2.3.x ` )
4043- Create a ` maintenance/X.Y.x ` (For example: ` maintenance/2.4.x ` from the ` v2.4.0 ` tag.)
4144
0 commit comments