@@ -13,13 +13,9 @@ the maintenance branch. If so, release a last patch release first. See
13
13
- Check the result of ` git diff vX.Y-1.Z' ChangeLog ` . (For example:
14
14
` git diff v2.3.4 ChangeLog ` )
15
15
- 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.
23
19
- Move the ` main ` branch up to a dev version with ` tbump ` :
24
20
25
21
``` bash
@@ -34,8 +30,15 @@ tbump 2.5.0-dev0 --no-tag --no-push
34
30
git commit -am " Upgrade the version to 2.5.0-dev0 following 2.4.0 release"
35
31
```
36
32
37
- Check the result and then upgrade the main branch
33
+ Check the commit and then push to a release branch
38
34
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.
39
42
- Delete the ` maintenance/X.Y-1.x ` branch. (For example: ` maintenance/2.3.x ` )
40
43
- Create a ` maintenance/X.Y.x ` (For example: ` maintenance/2.4.x ` from the ` v2.4.0 ` tag.)
41
44
0 commit comments