Skip to content

Automate Bazel Central Registry release workflow for tagged releases#585

Open
Rahul-Sutariya wants to merge 1 commit into
bmw-software-engineering:mainfrom
Rahul-Sutariya:bcr_auto_release_version_workflow
Open

Automate Bazel Central Registry release workflow for tagged releases#585
Rahul-Sutariya wants to merge 1 commit into
bmw-software-engineering:mainfrom
Rahul-Sutariya:bcr_auto_release_version_workflow

Conversation

@Rahul-Sutariya

@Rahul-Sutariya Rahul-Sutariya commented May 18, 2026

Copy link
Copy Markdown

Add release/publish pipelines, BCR templates, and docs to generate and publish BCR PRs automatically.

Note: To open BCR PRs through a fork, add a repository secret named BCR_PUBLISH_TOKEN in the lobster repository.
This secret must be a classic PAT (repo + workflow) from the GitHub account that owns (or can push to) the configured BCR fork, for example Rahul-Sutariya/bazel-central-registry.

@Rahul-Sutariya Rahul-Sutariya marked this pull request as ready for review May 18, 2026 11:52
@Rahul-Sutariya Rahul-Sutariya requested a review from a team as a code owner May 18, 2026 11:52
@Rahul-Sutariya Rahul-Sutariya force-pushed the bcr_auto_release_version_workflow branch from 2541cc6 to 69e63a9 Compare May 19, 2026 04:42
Comment thread .github/workflows/release_prep.sh Outdated
@Rahul-Sutariya Rahul-Sutariya force-pushed the bcr_auto_release_version_workflow branch from 69e63a9 to 51bfbd2 Compare May 20, 2026 05:34
@Rahul-Sutariya Rahul-Sutariya requested a review from phiwuu May 20, 2026 05:35
@Rahul-Sutariya

Copy link
Copy Markdown
Author

Hi @phiwuu, Cloud you please review this PR?

@Rahul-Sutariya Rahul-Sutariya force-pushed the bcr_auto_release_version_workflow branch 4 times, most recently from 26d4aba to 549840c Compare June 1, 2026 06:20
@Rahul-Sutariya Rahul-Sutariya force-pushed the bcr_auto_release_version_workflow branch from 549840c to d9176a6 Compare June 17, 2026 08:22
Add release/publish pipelines, BCR templates, and docs to generate and publish BCR PRs automatically.
@Rahul-Sutariya Rahul-Sutariya force-pushed the bcr_auto_release_version_workflow branch from d9176a6 to a2615f4 Compare June 30, 2026 12:13
Comment thread .github/workflows/release.yml Outdated
description: GitHub fork used to open the BCR PR (owner/repo)
required: false
type: string
default: Rahul-Sutariya/bazel-central-registry

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lets create a fork in bmw-software-engineering

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Version in Module Bazel out of synch

with:
tag_name: ${{ inputs.tag_name }}
registry_fork: ${{ inputs.registry_fork }}
draft: true

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No draft for bot users

Comment thread documentation/release.md
- Calls `.github/workflows/release_prep.sh` to build a source archive under `archives/` and generate release notes.
- Creates a **draft** GitHub release and uploads the archive as a release asset.
3. `.github/workflows/publish.yml` opens a pull request to the Bazel Central Registry via `publish-to-bcr`.
4. After the BCR PR is merged, the draft GitHub release is finalized.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also adapt here

Comment thread .bcr/presubmit.yml

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add test targets to presubmit:

bazel test //tests_unit/...
bazel test //tests_system/...
bazel test //tests_integration/...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants