Cross-repo precompiled-formula bump action (one formula in the monorepo tap) #14

Closed
opened 2026-06-04 05:24:30 +00:00 by coilysiren · 1 comment
Owner

Goal

A cross-repo Forgejo action that, after a release uploads assets, rewrites one named precompiled formula's per-platform url + sha256 and commits it to a Homebrew tap that lives in a different repo. Split out of #6 (and #8) because it is the shared dependency of every tool that lands in the monorepo, not o2r-specific work.

Why split

The existing coilysiren/agentic-os/actions/bump-formula only rewrites a single build-from-source url line in a formula in the same repo. The monorepo model needs three things it does not do:

  • Cross-repo write - the release runs in otel-a2a-relay-cli (or coily, repo-recall, ward) but the formula lives in coilyco-flight-deck/homebrew-tap. Needs CI_RELEASE_TOKEN and a checkout/commit/push of the tap repo.
  • One formula in a many-formula tap - target Formula/<tool>.rb by name, leave the sibling formulae untouched.
  • Per-platform bump - rewrite the url + sha256 for each on_macos/on_linux x on_arm/on_intel block from the release's <tool>-<os>-<arch> + .sha256 assets, not a single line.

Work

  • Extend or replace coilysiren/agentic-os/actions/bump-formula (or add a sibling action) to take: target tap repo, formula filename, release tag, and the asset-name pattern. Resolve each platform's .sha256, rewrite the formula, commit + push to the tap.
  • Wire it into the o2r release pipeline as the pilot consumer (the auto-bump step #6 calls).
  • Document the action inputs so coily + repo-recall reuse it unchanged when #8 migrates them.

Depends on

#6 (the tap repo + o2r formula must exist as the first target). Needs CI_RELEASE_TOKEN provisioned for coilyco-flight-deck repos (coilysiren/inbox#28, blocker #9).

Part of the o2r packaging epic (#5). Shared dependency of #6 and #8.

## Goal A cross-repo Forgejo action that, after a release uploads assets, rewrites one named precompiled formula's per-platform `url` + `sha256` and commits it to a Homebrew tap that lives in a **different** repo. Split out of #6 (and #8) because it is the shared dependency of every tool that lands in the monorepo, not o2r-specific work. ## Why split The existing `coilysiren/agentic-os/actions/bump-formula` only rewrites a single build-from-source `url` line in a formula in the same repo. The monorepo model needs three things it does not do: - **Cross-repo write** - the release runs in `otel-a2a-relay-cli` (or coily, repo-recall, ward) but the formula lives in `coilyco-flight-deck/homebrew-tap`. Needs `CI_RELEASE_TOKEN` and a checkout/commit/push of the tap repo. - **One formula in a many-formula tap** - target `Formula/<tool>.rb` by name, leave the sibling formulae untouched. - **Per-platform bump** - rewrite the `url` + `sha256` for each `on_macos`/`on_linux` x `on_arm`/`on_intel` block from the release's `<tool>-<os>-<arch>` + `.sha256` assets, not a single line. ## Work - Extend or replace `coilysiren/agentic-os/actions/bump-formula` (or add a sibling action) to take: target tap repo, formula filename, release tag, and the asset-name pattern. Resolve each platform's `.sha256`, rewrite the formula, commit + push to the tap. - Wire it into the o2r release pipeline as the pilot consumer (the auto-bump step #6 calls). - Document the action inputs so coily + repo-recall reuse it unchanged when #8 migrates them. ## Depends on #6 (the tap repo + o2r formula must exist as the first target). Needs `CI_RELEASE_TOKEN` provisioned for coilyco-flight-deck repos (coilysiren/inbox#28, blocker #9). Part of the o2r packaging epic (#5). Shared dependency of #6 and #8.
Author
Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.
coilysiren 2026-06-17 08:23:40 +00:00
Commenting is not possible because the repository is archived.
No description provided.