Publish [email protected]

[jchadwick-buf]

Release: https://github.com/bufbuild/protovalidate-cc/releases/tag/v1.0.0-rc.2

Automated by Publish to BCR

(Manually recreated because of CLA signing issues. Will need to resolve later...)

[bazel-io]

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (protovalidate-cc) have been updated in this PR.
Please review the changes. You can view a diff against the previous version in the "Generate module diff" check.

[jchadwick-buf]

P.S.: Can some BCR maintainer help us fix @bcr-buf failing the CLA checker? It is a machine user that we created to deal with limitations of the current publish to BCR workflow, but it seems like the normal way to mark the CLA as signed requires a gaia account. I'm pretty sure we'd rather not have to do that. See https://github.com/bazelbuild/bazel-central-registry/pull/4781/checks?check_run_id=43646364879 for the issue that happened that I'm manually working around for now.

[meteorcloudy]

I believe you have to login as bcr-buf and sign the CLA

[jchadwick-buf]

I see. I think that needs a Google account and bcr-buf doesn't actually have one. I'll see what I can do if there's really no easy way to just whitelist it. (I don't think it's that big of a deal to just make a new Google account here but it seems that it would require paying for both an outside collaborator on GitHub and a Google Workspace account just to have an automated BCR workflow... Even if it's not a huge issue, I think this ought to be rectified.)