@@ -31,7 +31,8 @@ To release a new version of pybind11:
31
31
fails due to a known flake issue, either ignore or restart CI.)
32
32
- Add a release branch if this is a new minor version
33
33
- ``git checkout -b vX.Y ``, ``git push -u origin vX.Y ``
34
- - Update tags
34
+ - Update tags (optional; if you skip this, the GitHub release makes a
35
+ non-annotated tag for you)
35
36
- ``git tag -a vX.Y.Z -m 'vX.Y.Z release' ``.
36
37
- ``git push --tags ``.
37
38
- Update stable
@@ -43,9 +44,10 @@ To release a new version of pybind11:
43
44
(Note: if you do not use an existing tag, this creates a new lightweight tag
44
45
for you, so you could skip the above step).
45
46
- GUI method: click "Create a new release" on the far right, fill in the tag
46
- name, fill in a release name like "Version X.Y.Z", and optionally
47
- copy-and-paste the changelog into the description (processed as markdown by
48
- Pandoc). Check "pre-release" if this is a beta/RC.
47
+ name (if you didn't tag above, it will be made here), fill in a release
48
+ name like "Version X.Y.Z", and optionally copy-and-paste the changelog into
49
+ the description (processed as markdown by Pandoc). Check "pre-release" if
50
+ this is a beta/RC.
49
51
- CLI method: with ``gh `` installed, run ``gh release create vX.Y.Z -t "Version X.Y.Z" ``
50
52
If this is a pre-release, add ``-p ``.
51
53
0 commit comments