• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

supabase / supabase-flutter / 27539879221
85%

Build:
DEFAULT BRANCH: main
Ran 15 Jun 2026 10:25AM UTC
Jobs 8
Files 73
Run time 1min
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

15 Jun 2026 10:23AM UTC coverage: 81.508%. Remained the same
27539879221

push

github

web-flow
ci: consolidate workflows and collect coverage during tests (#1406)

## What

Consolidate CI into a single `test.yml` workflow and stop re-running
every package just to collect coverage.

Closes SDK-1054.

## Why

Coverage was collected by a separate `coverage.yml` that re-ran every
package's tests serially in one ~30-minute job (`for d in */`), setting
up Docker again per package. This duplicated the work already done by
the per-package test workflows, which run `stable`/`beta`/`dev` but
collected no coverage. Tests effectively ran twice on every PR.

This mirrors how supabase-js structures its CI: coverage is collected
during the same runs that test for correctness, and a single job owns
the Coveralls `parallel-finished` step.

## How

- **`changes`** detects affected packages with melos (`melos list --diff
--include-dependents`), replacing the manual per-package path filters.
Transitive dependents are derived from the dependency graph (a
`realtime_client` change resolves to `realtime_client`, `supabase`,
`supabase_flutter`, matching the old filters). Falls back to all
packages when CI config, `melos.yaml`, `pubspec.lock`, or `infra/`
change, or on first push.
- **`test-dart`** runs affected Dart packages across
`stable`/`beta`/`dev`. Coverage is collected on the `stable` run (`dart
test --coverage` then `format_coverage`) and uploaded to Coveralls with
`parallel: true` and a per-package `flag-name`. Docker and concurrency
settings are carried over per package.
- **`test-flutter`** runs `supabase_flutter` when affected, collecting
coverage via `flutter test --coverage` on ubuntu/`3.x`, plus the
existing platform builds.
- **`coverage-finished`** is the single owner of Coveralls
`parallel-finished`, with `carryforward` so unaffected packages keep
their last coverage.
- **`test-result`** is an aggregating gate job.
- Removed `coverage.yml`, `dart-package-test.yml`, and the 8 per-package
workflow files.

## Required follow-up (repo settings)

- [ ] Upd... (continued)

3729 of 4575 relevant lines covered (81.51%)

3.15 hits per line

Jobs
ID Job ID Ran Files Coverage
1 postgrest - 27539879221.1 15 Jun 2026 10:26AM UTC 9
83.74
GitHub Action Run
2 realtime_client - 27539879221.2 15 Jun 2026 10:25AM UTC 11
74.87
GitHub Action Run
3 supabase - 27539879221.3 15 Jun 2026 10:25AM UTC 15
88.62
GitHub Action Run
4 supabase_flutter - 27539879221.4 15 Jun 2026 10:25AM UTC 7
78.57
GitHub Action Run
5 gotrue - 27539879221.5 15 Jun 2026 10:27AM UTC 23
80.06
GitHub Action Run
6 functions_client - 27539879221.6 15 Jun 2026 10:25AM UTC 2
97.1
GitHub Action Run
7 storage_client - 27539879221.7 15 Jun 2026 10:26AM UTC 5
93.01
GitHub Action Run
8 yet_another_json_isolate - 27539879221.8 15 Jun 2026 10:25AM UTC 1
79.03
GitHub Action Run
Source Files on build 27539879221
  • Tree
  • List 73
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #27539879221
  • e6b87107 on github
  • Prev Build on main (#27424656399)
  • Next Build on main (#27544768443)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc