Zengtudor/pybind11
1
0
Fork 0
mirror of https://github.com/pybind/pybind11.git synced 2024-11-22 13:15:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: post-release (#3128)

Browse Source
This commit is contained in:
Henry Schreiner 2021-07-17 11:50:42 -04:00 committed by GitHub
parent 65e95ea867
commit 74935f8d67
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 41 additions and 34 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/changelog.rst
View File

@ -6,6 +6,11 @@ Changelog
Starting with version 1.8.0, pybind11 releases use a `semantic versioning Starting with version 1.8.0, pybind11 releases use a `semantic versioning
<http://semver.org>`_ policy. <http://semver.org>`_ policy.
Next version (WIP)
------------------
v2.7.0 (Jul 16, 2021) v2.7.0 (Jul 16, 2021)
--------------------- ---------------------

6
docs/release.rst
View File

@ -15,7 +15,8 @@ For example:
For beta, ``PYBIND11_VERSION_PATCH`` should be ``Z.b1``. RC's can be ``Z.rc1``. For beta, ``PYBIND11_VERSION_PATCH`` should be ``Z.b1``. RC's can be ``Z.rc1``.
Always include the dot (even though PEP 440 allows it to be dropped). For a Always include the dot (even though PEP 440 allows it to be dropped). For a
final release, this must be a simple integer. final release, this must be a simple integer. There is also a HEX version of
the version just below.
To release a new version of pybind11: To release a new version of pybind11:
@ -24,6 +25,7 @@ To release a new version of pybind11:
- Update the version number - Update the version number
- Update ``PYBIND11_VERSION_MAJOR`` etc. in - Update ``PYBIND11_VERSION_MAJOR`` etc. in
``include/pybind11/detail/common.h``. PATCH should be a simple integer. ``include/pybind11/detail/common.h``. PATCH should be a simple integer.
- Update the version HEX just below, as well.
- Update ``pybind11/_version.py`` (match above) - Update ``pybind11/_version.py`` (match above)
- Ensure that all the information in ``setup.cfg`` is up-to-date, like - Ensure that all the information in ``setup.cfg`` is up-to-date, like
supported Python versions. supported Python versions.
@ -53,7 +55,7 @@ To release a new version of pybind11:
name like "Version X.Y.Z", and optionally copy-and-paste the changelog into name like "Version X.Y.Z", and optionally copy-and-paste the changelog into
the description (processed as markdown by Pandoc). Check "pre-release" if the description (processed as markdown by Pandoc). Check "pre-release" if
this is a beta/RC. You can get partway there with this is a beta/RC. You can get partway there with
``cat docs/changelog.rst | pandoc -f rst -t markdown``. ``cat docs/changelog.rst | pandoc -f rst -t gfm``.
- CLI method: with ``gh`` installed, run ``gh release create vX.Y.Z -t "Version X.Y.Z"`` - CLI method: with ``gh`` installed, run ``gh release create vX.Y.Z -t "Version X.Y.Z"``
If this is a pre-release, add ``-p``. If this is a pre-release, add ``-p``.

4
include/pybind11/detail/common.h
View File

@ -11,11 +11,11 @@
#define PYBIND11_VERSION_MAJOR 2 #define PYBIND11_VERSION_MAJOR 2
#define PYBIND11_VERSION_MINOR 7 #define PYBIND11_VERSION_MINOR 7
#define PYBIND11_VERSION_PATCH 0 #define PYBIND11_VERSION_PATCH 1.dev1
// Similar to Python's convention: https://docs.python.org/3/c-api/apiabiversion.html // Similar to Python's convention: https://docs.python.org/3/c-api/apiabiversion.html
// Additional convention: 0xD = dev // Additional convention: 0xD = dev
#define PYBIND11_VERSION_HEX 0x02070000 #define PYBIND11_VERSION_HEX 0x020701D1
#define PYBIND11_NAMESPACE_BEGIN(name) namespace name { #define PYBIND11_NAMESPACE_BEGIN(name) namespace name {
#define PYBIND11_NAMESPACE_END(name) } #define PYBIND11_NAMESPACE_END(name) }

2
pybind11/_version.py
View File

@ -8,5 +8,5 @@ def _to_int(s):
return s return s
__version__ = "2.7.0" __version__ = "2.7.1.dev1"
version_info = tuple(_to_int(s) for s in __version__.split(".")) version_info = tuple(_to_int(s) for s in __version__.split("."))