-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add pybind11_protobuf #2074
Add pybind11_protobuf #2074
Conversation
Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (pybind11_protobuf) have been updated in this PR. Please review the changes. |
@frigus02 do you accept maintainership? |
@fmeum could you please trigger the tests? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I accept the maintainership
f33ee96
to
174eba4
Compare
pybind/pybind11_protobuf#157 has been merged. Running |
9da447a
to
abf5dbc
Compare
modules/pybind11_protobuf/0.0.0-20240524-1d7a729/patches/module-dot-bazel-dev-dependency.patch
Show resolved
Hide resolved
8512abe
to
1e73952
Compare
1e73952
to
71682f8
Compare
@fmeum could you please have another look? Thanks! |
This is using the same patches as in bazelbuild#2031. As there is no release process, we are using a version string including the commit sha like it's done for `boringssl` as well.
This is using the same patches as in bazelbuild#2031. As there is no release process, we are using a version string including the commit sha like it's done for `boringssl` as well.
This is using the same patches as in #2031.
As there is no release process, we are using a version string including the commit sha like it's done for
boringssl
as well.