Publishing to the Bazel Central Registry

[mbland]

Is there any objection to reviving #313 to add the publish-to-bcr workflow and begin publishing to the BCR? That would help unblock one of the open source modules I help maintain, which now depends on bazel_remote_apis via a git_override:

• https://github.com/EngFlow/engflowapis/blob/2026.02.26-17.03.31/go/MODULE.bazel#L76-L82
• {engflowapis,engflowapis-go,engflowapis-java}@2026.02.26-17.03.31 bazel-central-registry#7718
• BCR Presubmit #28978

#313 has been dormant for a year; I'm happy to pick up the effort if need be.

cc: @Wyverald @bergsieker

[EdSchouten]

I have an anti-objection to this!

[sluongng]

My understanding is that the old GitHub App approach is going away. And the new workflows approach is added https://github.com/bazel-contrib/publish-to-bcr

If you want to explore doing this, there are some existing examples here https://github.com/search?q=org%3Abazelbuild+path%3A.github%2Fworkflows%2Fpublish.yaml&type=code
(a bit inconsistent between different push remotes currently, so I would love to know which one would work best for the remote-apis repo)

[mbland]

Just posted #370.