Skip to content

Migrate from Publish to BCR app to workflow#50

Merged
fmeum merged 1 commit intobazel-contrib:mainfrom
fmeum:migrate-publish-to-bcr-workflow
Mar 13, 2026
Merged

Migrate from Publish to BCR app to workflow#50
fmeum merged 1 commit intobazel-contrib:mainfrom
fmeum:migrate-publish-to-bcr-workflow

Conversation

@fmeum
Copy link
Copy Markdown
Member

@fmeum fmeum commented Mar 13, 2026

Summary

  • Add .github/workflows/publish.yaml that uses the bazel-contrib/publish-to-bcr reusable workflow to automate BCR publishing after releases
  • Update release.yml to call the new publish workflow after a successful release and bump release_ruleset from v6 to v7.2.2
  • Add required permissions for artifact attestations (id-token: write, attestations: write)

🤖 Generated with Claude Code

@google-cla
Copy link
Copy Markdown

google-cla Bot commented Mar 13, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Replace the GitHub App-based BCR publishing with the reusable workflow
from bazel-contrib/publish-to-bcr. This adds a new publish.yaml workflow
that runs after a successful release, and updates release.yml to call it.

Also updates the release_ruleset reusable workflow from v6 to v7.2.2 and
adds the required permissions for artifact attestations.
@fmeum fmeum force-pushed the migrate-publish-to-bcr-workflow branch from 15b37bb to d450e1f Compare March 13, 2026 11:30
@fmeum fmeum requested review from Wyverald and meteorcloudy March 13, 2026 11:30
@fmeum fmeum enabled auto-merge (squash) March 13, 2026 11:37
@fmeum fmeum merged commit 81c0071 into bazel-contrib:main Mar 13, 2026
2 checks passed
@fmeum fmeum deleted the migrate-publish-to-bcr-workflow branch March 13, 2026 13:39
@fmeum
Copy link
Copy Markdown
Member Author

fmeum commented Mar 13, 2026

@meteorcloudy Publishing failed since we aren't in bazel-contrib - should we just move the repo to that org? It seems easier to maintain that way and we aren't using Bazel CI anyway.

@meteorcloudy
Copy link
Copy Markdown
Collaborator

Done!

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.

2 participants