Releasing

Prelude: version numbers

Because pybind11_bazel is "just" Bazel fu layered over pybind11, our convention is that pybind11_bazel version numbers should mirror pybind11 version numbers. Please refer to https://github.com/pybind/pybind11/releases if at all in doubt!

Releasing

• Update the version number.

  • Update the module()'s X.Y.Z version number in MODULE.bazel.
    • Please double-check that this is the same as the pybind11 version number!
  • git add, git commit, git push

• Create the new tag.

  • git tag -a vX.Y.Z -m 'vX.Y.Z release'
  • git push --tags
  • From the Tags page, download the .zip and the .tar.gz for the new tag.

• Create the new release.

  • From the Releases page, click the Draft a new release button.
  • On the New release page, select the new tag, attach the .zip and the .tar.gz for the new tag and click the Publish release button.

• Tell junyer to poke the new release into BCR.

  • https://github.com/bazelbuild/bazel-central-registry/tree/main/modules/pybind11_bazel
  • junyer still needs to document this step properly. ;)