Nicholas Junge
986423a62d
* Supply MacOS deployment target to delocate, use build+uv frontend This shaves off multiple minutes from the wheel builds alone. Also revert to trusted publishing for wheel uploads as it is now set up. * Bump oldest supported Python to 3.10, eliminate setuptools-scm The version is now a string again, under the same attribute as it was before. This is a pragmatic decision in order to be able to upload wheels again, possibly directly from main. We could in the future also set the Python version to a development version if we want to avoid accidental uploads of `main`. * Add a note on supported Python versions in the docs Also fixes the setuptools failure observed in the latest CI by pinning to the last version before v73 until the problem is identified and resolved.
1.2 KiB
1.2 KiB
How to release
- Make sure you're on main and synced to HEAD
- Ensure the project builds and tests run
parallel -j0 exec ::: test/*_testcan help ensure everything at least passes
- Prepare release notes
git log $(git describe --abbrev=0 --tags)..HEADgives you the list of commits between the last annotated tag and HEAD- Pick the most interesting.
- Create one last commit that updates the version saved in
CMakeLists.txt,MODULE.bazel, andbindings/python/google_benchmark/__init__.pyto the release version you're creating. (This version will be used if benchmark is installed from the archive you'll be creating in the next step.)
# CMakeLists.txt
project (benchmark VERSION 1.9.0 LANGUAGES CXX)
# MODULE.bazel
module(name = "com_github_google_benchmark", version="1.9.0")
# google_benchmark/__init__.py
__version__ = "1.9.0"
- Create a release through github's interface
- Note this will create a lightweight tag.
- Update this to an annotated tag:
git pull --tagsgit tag -a -f <tag> <tag>git push --force --tags origin
- Confirm that the "Build and upload Python wheels" action runs to completion
- Run it manually if it hasn't run.