Skip to content

chore: serve the formula from approov-cli releases (structural change only) - #12

Open
ivolz wants to merge 1 commit into
mainfrom
chore/formula-from-approov-cli-releases
Open

chore: serve the formula from approov-cli releases (structural change only)#12
ivolz wants to merge 1 commit into
mainfrom
chore/formula-from-approov-cli-releases

Conversation

@ivolz

@ivolz ivolz commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

Important

This is a structural change only — it is not the 3.6.1 update.
Merge it to main on its own; the release pipeline then opens the 3.6.1 formula-bump PR
automatically. No tag or release is needed in this repository, now or ever again.

📦 What this changes

The tap currently does two jobs: it holds the formula and hosts the release tarballs
(3.6.0, 3.5.0, 3.4.0…). After this it holds only the formula, which is what a tap should be.

Binaries come from approov/approov-cli
the single origin for every installation artifact and all installation documentation across
macOS, Windows and Linux. Homebrew, Scoop and winget all resolve against that one repository, so
there is one place to look for downloads, checksums, signatures and install instructions.

🔧 Details

Change Why
urlapproov-cli releases Stops this repo hosting binaries; one origin for all platforms
Per-OS install blocks New releases ship one tarball per platform with a bare approov at the root; the old single tarball had Linux/ and MacOS/ subdirectories
One url + checksum for macOS The macOS build is universal — Apple silicon and Intel share it
license and a real test do brew audit --strict requires both
README rewritten Describes the tap as formula-only and points at the releases repo; adds support@approov.io

Warning

brew install will not work between this merge and the 3.6.1 release landing.
The version and checksums here come from a temporary pipeline-test build, and
approov/approov-cli is still internal, so the URLs
are not anonymously reachable. This window is expected and accepted. Existing installations
are unaffected — only new brew install / brew upgrade runs are.

✅ Merge checklist

  • Formula and README reviewed
  • Understood that brew install is broken until the 3.6.1 PR lands

Deliberately not required before merging — the automation handles them:

  • version and checksums (the 3.6.1 PR sets both from that release's SHA256SUMS)
  • brew audit / brew install verification (do it on the 3.6.1 PR, when the URLs resolve)

🤖 What happens next

  1. This merges — main now has the right structure and the wrong version. Expected.
  2. approov/approov-cli is made public.
  3. 3.6.1 is tagged and released.
  4. The pipeline opens the formula-bump PR automatically, with version and both sha256 read
    straight from that release's SHA256SUMS, so the formula cannot disagree with what was
    published. Verify with brew audit --strict --online on that PR.
  5. Merging it restores brew install and completes the migration.

main keeps requiring an approving review, so those PRs still need a human merge — deliberately,
so someone sees the diff before customers receive it.

Existing releases in this repo are left in place so any pinned installs keep working.

Tracked in approov/core-project-approov#675.

The tap currently hosts its own release tarballs and the formula points at
them, so it is doing two jobs. Binaries now come from the approov/approov-cli
release repository, published alongside the Windows and Linux packages with
checksums and a detached PGP signature, and this tap holds only the formula.

The old single tarball carried Linux/approov and MacOS/approov; the new
releases ship one tarball per platform with a bare approov at the root, so
the install block becomes per-OS. macOS is a universal binary, so Apple
silicon and Intel share one url and checksum.
@ivolz ivolz changed the title chore: take binaries from approov-cli releases (do not merge until public) chore: serve the formula from approov-cli releases (structural change only) Aug 2, 2026
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