Skip to content

chore(release): v0.1.0 — BCR-ready#1

Merged
michael-herwig merged 2 commits into
mainfrom
release/v0.1.0
Jul 2, 2026
Merged

chore(release): v0.1.0 — BCR-ready#1
michael-herwig merged 2 commits into
mainfrom
release/v0.1.0

Conversation

@michael-herwig

Copy link
Copy Markdown
Contributor

Prepares rules_ocx for Bazel Central Registry publication and cuts the first release.

BCR readiness

  • Add e2e/bzlmod, a downstream consumer module wired into .bcr/presubmit.yml as bcr_test_module. Lazy, digest-pinned ocx.package → presubmit builds the launcher with no OCI registry pull, keeping the BCR platform matrix reliable.
  • Rewrite presubmit.yml to the bcr_test_module form. The old top-level build ran rules_ocx as the root module, firing the dogfooding ocx.project dev tags (network provisioning) in BCR CI. As a non-root dep those dev tags are ignored.
  • Fix .bcr/metadata.template.json homepage + repository after the bazel-ocxrules_ocx rename.
  • .bazelignore += e2e; ignore the nested module's generated lock.

Release

  • Bump MODULE.bazel version 0.0.00.1.0 (matches tag v0.1.0; release.yml asserts this).

Verified

  • 14 unit + docs tests pass · buildifier clean
  • git archive at tag: strip_prefix rules_ocx-0.1.0/ matches source template; archive contains .bcr/ + e2e/bzlmod + MODULE
  • Test module builds from the extracted release archive (exactly BCR presubmit's path)

After merge

  1. git push origin v0.1.0 → fires release.yml (archive + integrity + GH release)
  2. Install the publish-to-bcr GitHub App on ocx-sh/rules_ocx → auto-opens the BCR PR

Make the repository publishable to the Bazel Central Registry via
publish-to-bcr.

- Add e2e/bzlmod, a downstream consumer module wired into .bcr/presubmit.yml
  as bcr_test_module. It uses a lazy, digest-pinned ocx.package so presubmit
  builds the launcher without pulling tool content from an OCI registry,
  keeping the BCR platform matrix reliable.
- Rewrite presubmit.yml to the bcr_test_module form. The prior top-level
  build ran rules_ocx as the root module, which fires the dogfooding
  ocx.project dev tags and would provision the dev toolchain over the
  network in BCR CI. As a non-root dep those dev tags are ignored.
- Fix .bcr/metadata.template.json homepage and repository after the
  bazel-ocx -> rules_ocx rename.
- Ignore the nested e2e module in the root build and its generated lock.
@michael-herwig michael-herwig merged commit d15034f into main Jul 2, 2026
14 checks passed
@michael-herwig michael-herwig deleted the release/v0.1.0 branch July 2, 2026 18:43
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.

1 participant