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!
    • The pybind11_bazel version should typically just be the pybind11 version, but can end with .bzl.<N> if the Bazel plumbing was updated separately.
  • git add, git commit, git push

• Create the new tag.

  • git tag -a vX.Y.Z -m 'vX.Y.Z release'
  • git push --tags

• The new release will be created automatically via GitHub Actions.

  • https://github.com/pybind/pybind11_bazel/blob/master/.github/workflows/release.yml

• 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. ;)