Protocol Buffers - Google's data interchange format (grpc依赖) https://developers.google.com/protocol-buffers/

Alex Eagle d2b71b347d feat: automate publishing releases to Bazel Central Registry (#16014 An error occurred ) Note, recent releases on the BCR have a patch set applied, and it seems these patches are developed independently to "fix" each protobuf release, rather than make changes to protobuf repo. The effect of this PR will be to create a broken publish to BCR for each protobuf release. At least this red PR on BCR will be our indication that the patches need to be manually replayed there. In parallel, starting with #16013 An error occurred I'll apply as many of those patches to the protobuf repo as possible. That will reduce the manual effort for each release. Replaces https://github.com/protocolbuffers/protobuf/pull/14565 which originated from my fork so the tests wouldn't run. Closes #16014 An error occurred COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/16014 from protocolbuffers:bcr `e17d9c8127` PiperOrigin-RevId: 615026796		12 months ago
..
README.md	feat: automate publishing releases to Bazel Central Registry (#16014 An error occurred )	12 months ago
metadata.template.json	feat: automate publishing releases to Bazel Central Registry (#16014 An error occurred )	12 months ago
presubmit.yml	feat: automate publishing releases to Bazel Central Registry (#16014 An error occurred )	12 months ago
source.template.json	feat: automate publishing releases to Bazel Central Registry (#16014 An error occurred )	12 months ago

Bazel Central Registry

When protobuf is released, we want it to be published to the Bazel Central Registry automatically: https://registry.bazel.build

This folder contains configuration files to automate the publish step. See https://github.com/bazel-contrib/publish-to-bcr/blob/main/templates/README.md for authoritative documentation about these files.