@@ -22,6 +22,9 @@ the version just below.
22
22
To release a new version of pybind11:
23
23
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
24
24
25
+ If you don't have nox, you should either use ``pipx run nox `` instead, or use
26
+ ``pipx install nox `` or ``brew install nox `` (Unix).
27
+
25
28
- Update the version number
26
29
- Update ``PYBIND11_VERSION_MAJOR `` etc. in
27
30
``include/pybind11/detail/common.h ``. PATCH should be a simple integer.
@@ -51,14 +54,12 @@ To release a new version of pybind11:
51
54
notifications to users watching releases, and also uploads PyPI packages).
52
55
(Note: if you do not use an existing tag, this creates a new lightweight tag
53
56
for you, so you could skip the above step.)
54
-
55
57
- GUI method: Under `releases <https://github.com/pybind/pybind11/releases >`_
56
58
click "Draft a new release" on the far right, fill in the tag name
57
59
(if you didn't tag above, it will be made here), fill in a release name
58
60
like "Version X.Y.Z", and copy-and-paste the markdown-formatted (!) changelog
59
61
into the description (usually ``cat docs/changelog.rst | pandoc -f rst -t gfm ``).
60
62
Check "pre-release" if this is a beta/RC.
61
-
62
63
- CLI method: with ``gh `` installed, run ``gh release create vX.Y.Z -t "Version X.Y.Z" ``
63
64
If this is a pre-release, add ``-p ``.
64
65
@@ -90,9 +91,7 @@ If you need to manually upload releases, you can download the releases from the
90
91
91
92
.. code-block :: bash
92
93
93
- python3 -m pip install build
94
- python3 -m build
95
- PYBIND11_SDIST_GLOBAL=1 python3 -m build
94
+ nox -s build
96
95
twine upload dist/*
97
96
98
97
This makes SDists and wheels, and the final line uploads them.
0 commit comments