Skip to content

ci: auto-publish releases to the BCR via reusable workflow - #34

Merged
helly25 merged 1 commit into
mainfrom
ci/bcr-publish
Jun 14, 2026
Merged

ci: auto-publish releases to the BCR via reusable workflow#34
helly25 merged 1 commit into
mainfrom
ci/bcr-publish

Conversation

@helly25

@helly25 helly25 commented Jun 14, 2026

Copy link
Copy Markdown
Owner

Rolls out the BCR auto-publish workflow to bzl (after verifying it end-to-end on bashtest → draft BCR PR bazelbuild/bazel-central-registry#9275).

  • publish.yaml: calls bazel-contrib/publish-to-bcr/.github/workflows/publish.yaml@v1.4.1, registry_fork: helly25/bazel-central-registry, draft PR, URL-based integrity.
  • release.yml: publish job needs: release, grants contents: write.

Uses the corrected permission pattern (publish job grants contents: write; no top-level read-all in the wrapper) — the cascade that startup-failed bashtest twice. BCR_PUBLISH_TOKEN is already set on this repo.

After merge, the next tagged release (0.4.4) opens a draft BCR PR for helly25_bzl. bzl's release produces SLSA attestations; can flip attest: true later to have the BCR verify them.

Mirror bashtest: add publish.yaml (bazel-contrib/publish-to-bcr@v1.4.1,
registry_fork helly25/bazel-central-registry, draft PR, URL-based
integrity) and hook it into release.yml after the release job. Replaces
the retired publish-to-bcr GitHub App.

Permissions match the proven pattern: the publish job grants contents:
write (a called reusable workflow can't exceed the caller's grant) and
publish.yaml carries no top-level read-all.
@helly25
helly25 requested a review from Fab-Cat June 14, 2026 17:38
@helly25
helly25 merged commit 0532b18 into main Jun 14, 2026
11 checks passed
@helly25
helly25 deleted the ci/bcr-publish branch June 14, 2026 17:39
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