protobuf@27.0-rc2

[publish-to-bcr-bot]

Release: https://github.com/protocolbuffers/protobuf/releases/tag/v27.0-rc2

Automated by Publish to BCR

[bazel-io]

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (protobuf) have been updated in this PR. Please review the changes.

[zhangskz]

@alexeagle Do you know how the extra version = v27.0-rc2 is coming from? MODULE.bazel looks right in v27.0-rc2 afaict: https://github.com/protocolbuffers/protobuf/blob/v27.0-rc2/MODULE.bazel

I tried removing the spurious line in my latest commit but looks like it still fails validation: https://buildkite.com/bazel/bcr-presubmit/builds/5311#018f5e4e-92bf-48e2-9759-365059be2888

Sidenote: Looks like release successfully triggers this PR from publish-to-br-bot! Thanks for your contribution here!

[alexeagle]

@kormide is the person to ask. I think it's a publish-to-bcr bug that it adds a version field instead of modifying the one that's there, probably because it's referencing a constant and every other module uses a string literal as the version value

[zhangskz]

Thanks -- removed from the PR. I can probably update our version line to remove the const instead although we use this to make things easier for our version updaters. Would a comment on this line interfere with the tooling?

e.g.

version = "27.0-rc2" # com_google_protobuf version

Per chat, sounds like it can also handle the following as well?

version = "0.0.0"

[zhangskz]

@fmeum Can you take another look at this change?

Note, I had to remove debian 10 from presubmit.yml due to a warning being treated as an error by c11plus -- is there a way to simply disable warnings from being treated as errors here?

[fmeum]

Note, I had to remove debian 10 from presubmit.yml due to a warning being treated as an error by c11plus -- is there a way to simply disable warnings from being treated as errors here?

You can pass flags just as in regular Bazel CI. There are no defaults beyond what Bazel's or your repo's C++ toolchains provide, so I'm a bit surprised to see this.

[fmeum]

Is this really the plan? Afaik toolchain types can't be aliased, so this would be somewhat painful.