[bazel/infra] Add manual BCR release workflow#567
Merged
shameekganguly merged 1 commit intogz-sensors10from Jan 2, 2026
Merged
[bazel/infra] Add manual BCR release workflow#567shameekganguly merged 1 commit intogz-sensors10from
shameekganguly merged 1 commit intogz-sensors10from
Conversation
Signed-off-by: Shameek Ganguly <shameek@intrinsic.ai>
iche033
approved these changes
Dec 16, 2025
Contributor
Author
|
@Mergifyio backport main gz-sensors9 |
Contributor
✅ Backports have been createdDetails
|
mergify bot
pushed a commit
that referenced
this pull request
Jan 2, 2026
Adds the publish.yaml workflow to release a tag to the Bazel Central Registry (BCR). This workflow uses the official reusable publish-to-bcr workflow from the bazel team. Signed-off-by: Shameek Ganguly <shameek@intrinsic.ai> (cherry picked from commit 14051ea)
10 tasks
mergify bot
pushed a commit
that referenced
this pull request
Jan 2, 2026
Adds the publish.yaml workflow to release a tag to the Bazel Central Registry (BCR). This workflow uses the official reusable publish-to-bcr workflow from the bazel team. Signed-off-by: Shameek Ganguly <shameek@intrinsic.ai> (cherry picked from commit 14051ea)
10 tasks
shameekganguly
added a commit
that referenced
this pull request
Jan 6, 2026
Adds the publish.yaml workflow to release a tag to the Bazel Central Registry (BCR). This workflow uses the official reusable publish-to-bcr workflow from the bazel team. (cherry picked from commit 14051ea) Signed-off-by: Shameek Ganguly <shameek@intrinsic.ai> Co-authored-by: Shameek Ganguly <shameek@intrinsic.ai>
shameekganguly
added a commit
that referenced
this pull request
Jan 6, 2026
Adds the publish.yaml workflow to release a tag to the Bazel Central Registry (BCR). This workflow uses the official reusable publish-to-bcr workflow from the bazel team. (cherry picked from commit 14051ea) Signed-off-by: Shameek Ganguly <shameek@intrinsic.ai> Co-authored-by: Shameek Ganguly <shameek@intrinsic.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Internal tooling
Summary
Adds the
publish.yamlworkflow to release a tag to the Bazel Central Registry (BCR). This workflow uses the official reusablepublish-to-bcrworkflow from the bazel team.For now, the workflow must be triggered manually. Once we have iron'ed out any unforeseen issues over a few releases, we can tie it to our release automation.
The following template files are added to mirror the existing files in the latest manual bcr release for gz-sensors.
.bcr/metadata.template.json.bcr/presubmit.yml.bcr/source.template.jsonSome of the fields are auto-populated by
publish-to-bcrbased on the repo details when creating a PR in BCR.Note that MODULE.bazel will be auto-patched by
publish-to-bcrto insert the new version based on the tag e.g. taggz-sensors10_10.0.0--> version10.0.0. This version will also be added tometadata.jsonalongside existing versions.Testing
This PR mirrors the BCR setup for gz-utils: gazebosim/gz-utils#192. See testing instructions there.
Checklist
codecheckpassed (See contributing)Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining
Signed-off-byandGenerated-bymessages.