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

supabase / cli / 40861200762
47%
develop: 46%

Build:
Build:
LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7380-74d4774766936b6e6141a58d061c3396a01c85c9
DEFAULT BRANCH: develop
Ran 29 Oct 2026 10:55AM UTC
Jobs 1
Files 119
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

29 Oct 2026 10:53AM UTC coverage: 46.568%. Remained the same
40861200762

push

github

web-flow
feat(config): publish the config schemas as draft-07 under supabase.com/schemas (#7366)

## Summary

The config, project-config and `supabase.lock` schemas declared draft
2020-12, and their `$id`s pointed at `supabase.com/docs/cli/...`, which
404s. Taplo (Even Better TOML) doesn't support anything newer than
draft-07, and the schemas only use keywords draft-07 already has. So
this moves all three to draft-07, with `$id`s at the URLs they'll be
hosted at.

- `toPublishedJsonSchemaDocument` and the lock schema now go through
Effect's `JsonSchema.toDocumentDraft07`. That converter turns `$defs`
into `definitions`, rewrites the refs, and throws on anything draft-07
can't represent rather than dropping it
- The `$id`s move to
`https://supabase.com/schemas/{config,project-config,supabase-lock}/v1.json`.
Nothing is served there yet. CLI-2865 sets up the path in
supabase/supabase and CLI-2864 publishes to it on stable releases
- The committed copies move from `apps/docs/public/cli/*.schema.json` to
`apps/docs/public/schemas/<name>/v1.json`. That's the same layout as the
hosted URLs, so the publisher can copy the folder across as-is
- `supabase.lock` keeps being written with its original `$schema` value,
because older CLIs check that field as a literal and would reject
anything else. Reads also accept the hosted URL
(`HOSTED_LOCK_SCHEMA_URL`), so a later release can switch writes over
once enough CLIs read it
- New `apps/cli/scripts/published-schemas.unit.test.ts` runs in the
existing unit job. It fails when a committed schema:
  - uses a keyword newer than draft-07
  - has a ref to `#/$defs/`
  - has an `$id` that doesn't match its file path
  - has drifted from what the source renders
- The lock schema committed on develop was already behind the `Lock`
schema. Regenerating it also brings in the current shape (no
`ArtifactPin`). The per-service `ServiceLock` schemas render
identically, so the published schema collapses them into one definition

## Schema shap... (continued)

5591 of 12006 relevant lines covered (46.57%)

25.09 hits per line

Jobs
ID Job ID Ran Files Coverage
1 40861200762.1 29 Oct 2026 10:55AM UTC 119
46.57
GitHub Action Run
Source Files on build 40861200762
  • Tree
  • List 119
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #40861200762
  • b0f10166 on github
  • Prev Build on gh-readonly-queue/develop/pr-7388-480345c70ae106395ee69ada32d0d659ebb3ffab (#40858874818)
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