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

supabase / supabase-swift / 31541604055
84%

Build:
DEFAULT BRANCH: main
Ran 11 Aug 2026 10:19PM UTC
Jobs 1
Files 102
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

11 Aug 2026 10:15PM UTC coverage: 84.694% (+0.1%) from 84.559%
31541604055

push

github

web-flow
ci: pin sync-compliance sdk-ref to current supabase/sdk main (#1195)

* chore: sync new capability IDs from canonical spec

* chore: drop stale duplicate capability IDs, pin sync to current sdk main

The 5 IDs the sync bot added (auth.sign_in.reset_password,
realtime.channel.send, storage.file_buckets.list_files_paginated,
storage.analytics.iceberg_namespace, storage.analytics.iceberg_table) are
not new — they're the pre-rename names already retired in 450a8fc (#1184)
per supabase/sdk#74.

The bot resynced them because our caller workflow doesn't override the
reusable workflow's sdk-ref input, so it inherits that pinned commit's
baked-in default (faba359a, 2026-07-20), which predates the #74 rename.
Pinning sdk-ref explicitly to a current supabase/sdk main SHA fixes the
root cause.

* ci: track supabase/sdk main for sync-compliance sdk-ref

supabase/sdk is internal (same org, same review process), so treating it
like an untrusted third party by pinning to a SHA isn't buying safety
here. It does cost freshness: the reusable workflow's own baked-in
sdk-ref default is a one-time pin upstream never refreshes, and
supabase/sdk has no tags/releases for anything to key an auto-bump off
of, so a fixed SHA here would just go stale again on its own schedule.
Tracking main avoids that.

* chore: drop explanatory comment from sdk-ref

* ci: bump sync-sdk-compliance pin to the sdk-ref: main fix

supabase/sdk#79 fixes the reusable workflow's own sdk-ref default (was
stuck on the stale faba359a pin since 2026-07-20). Point at that fix
commit directly and drop our local sdk-ref: main override, since it's
now the workflow's default.

Note: 72fda7c is currently on supabase/sdk's unmerged PR #79. Re-pin to
the actual main commit once that merges.

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Guilherme Souza <guilherme@supabase.io>

8787 of 10375 relevant lines covered (84.69%)

39.88 hits per line

Coverage Regressions

Lines Coverage ∆ File
3
97.35
-2.65% Sources/Helpers/AnyJSON/AnyJSON.swift
Jobs
ID Job ID Ran Files Coverage
1 31541604055.1 11 Aug 2026 10:19PM UTC 102
84.69
GitHub Action Run
Source Files on build 31541604055
  • Tree
  • List 102
  • Changed 2
  • Source Changed 0
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #31541604055
  • 7ae89b89 on github
  • Prev Build on main (#31194585392)
  • Next Build on main (#31579350572)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc