@@ -26,7 +26,8 @@ A bug-fix release is always done from a maintenance branch, so for example to re
26
26
27
27
Where ``5.1.x `` is the maintenance branch for the ``5.1 `` series.
28
28
29
- The automated workflow will publish a PR and notify it as a comment in the issue.
29
+ The automated workflow will publish a PR for a branch ``release-5.1.2 ``
30
+ and notify it as a comment in the issue.
30
31
31
32
Minor releases
32
33
^^^^^^^^^^^^^^
@@ -41,7 +42,8 @@ Minor releases
41
42
42
43
@pytestbot please prepare release from 5.2.x
43
44
44
- The automated workflow will publish a PR and notify it as a comment in the issue.
45
+ The automated workflow will publish a PR for a branch ``release-5.2.0 `` and
46
+ notify it as a comment in the issue.
45
47
46
48
Major and release candidates
47
49
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -60,7 +62,8 @@ Major and release candidates
60
62
61
63
@pytestbot please prepare release candidate from 6.0.x
62
64
63
- The automated workflow will publish a PR and notify it as a comment in the issue.
65
+ The automated workflow will publish a PR for a branch ``release-6.0.0 `` and
66
+ notify it as a comment in the issue.
64
67
65
68
At this point on, this follows the same workflow as other maintenance branches: bug-fixes are merged
66
69
into ``master `` and ported back to the maintenance branch, even for release candidates.
@@ -101,9 +104,10 @@ Releasing
101
104
Both automatic and manual processes described above follow the same steps from this point onward.
102
105
103
106
#. After all tests pass and the PR has been approved, tag the release commit
104
- in the ``MAJOR.MINOR.x `` branch and push it. This will publish to PyPI::
107
+ in the ``release- MAJOR.MINOR.PATCH `` branch and push it. This will publish to PyPI::
105
108
106
- git tag MAJOR.MINOR.PATCH
109
+ git fetch --all
110
+ git tag MAJOR.MINOR.PATCH upstream/release-MAJOR.MINOR.PATCH
107
111
git push [email protected] :pytest-dev/pytest.git MAJOR.MINOR.PATCH
108
112
109
113
Wait for the deploy to complete, then make sure it is `available on PyPI <https://pypi.org/project/pytest >`_.
0 commit comments