supabase / cli / 27747325128 / 1
65%
develop: 65%

LAST BUILD BRANCH: gh-readonly-queue/develop/pr-5642-893960a6e9fae412eb0215afae05f1348e356e62
DEFAULT BRANCH: develop
Ran
Files 225
Run time 6s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 65.033%. Remained the same
27747325128.1

push

github

web-flow 
ci: add post-publish install channel verification workflow (#5605)

Add automated end-to-end verification that published install channels
(Homebrew, Scoop, and curl|bash install script) successfully install the
released CLI and serve artifacts with matching checksums.

## Summary

This adds a new `verify-install-channels.yml` workflow that runs real
`brew install`, `scoop install`, and install-script installs against the
just-published channels, then verifies the installed version matches.
The workflow is triggered automatically after successful Homebrew and
Scoop publishes, and can also be manually dispatched for debugging
install regressions.

## Key Changes

- **New workflow**: `.github/workflows/verify-install-channels.yml`
- Homebrew job: installs from the supabase/tap on macOS, verifies
version
- Scoop job: installs from the supabase/scoop-bucket on Windows,
verifies version
- Install script job: runs `./install` on Linux and macOS, verifies
version
- Each job verifies the installed `supabase --version` matches the
released version
  - Accepts `version`, `brew_name`, and `scoop_name` as workflow inputs

- **Integration into release pipeline**: Modified
`.github/workflows/release-shared.yml`
- Added `verify-install-channels` job that runs after successful
`publish-homebrew` and `publish-scoop`
- Non-gating: runs last so failures surface as post-release signals
rather than blocking distribution
- Only runs for beta/stable channels (skipped for alpha and dry-run
releases)

- **Documentation**: Updated `apps/cli/docs/release-process.md`
  - Added `verify-install-channels` to the release flowchart
  - Documented the post-publish verification step and its purpose
- Explained that it catches regressions like v2.107.0 where brew/scoop
checksums mismatched the release tarballs

## Implementation Details

The workflow catches checksum mismatches that would cause real user
installs to fail, since brew, scoop, and the install script all verify
published che... (continued)

10748 of 16527 relevant lines covered (65.03%)

7.39 hits per line

Source Files on job 27747325128.1