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

supabase / cli / 40522106715
47%
develop: 46%

Build:
Build:
LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7380-74d4774766936b6e6141a58d061c3396a01c85c9
DEFAULT BRANCH: develop
Ran 27 Oct 2026 02:33PM 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

27 Oct 2026 02:32PM UTC coverage: 46.568%. Remained the same
40522106715

push

github

web-flow
feat(config): accept env() on number, boolean, enum and list fields in the config schema (#7333)

## Summary

The config loader resolves `env(VAR)` on any field and then coerces it
to the field's type, but the published `config.schema.json` typed
number, integer, boolean, enum and string-list fields strictly. So
`max_rows = "env(MAX_ROWS)"` loads fine but shows as an error in the
editor.

Those fields now accept either their usual value or a string matching
the loader's `env()` syntax. A mistyped literal like `max_rows = "1000"`
or `pool_mode = "statement"` still fails.

- `toPublishedJsonSchemaDocument` takes an `acceptEnvReferences` option,
and the CLI config schema turns it on. Each affected field becomes an
`anyOf` of its original type and an `env()` string, with `description`,
`default` and `examples` kept on the outer node so hover docs look the
same
- String lists such as `auth.additional_redirect_urls` accept an `env()`
string in place of the whole list, since the CLI splits the resolved
value on commas. Lists of enums don't, as the loader doesn't split those
- Fields that are already a union (e.g. `storage.file_size_limit`) get
one extra `env()` branch rather than a nested one
- `project-config.schema.json` doesn't change, since it describes values
after `env()` has been resolved
- `apps/docs/public/cli/config.schema.json` is regenerated
- `ajv` is added as a dev dependency of `@supabase/config` so tests can
check the published schema against what the loader accepts

## Schema shape change

If you generate types or other tooling from `config.schema.json`, the
affected fields now read as a union: their `type` moves from the field
itself into the first `anyOf` branch, next to the `env()` branch.
Configs that validated before still validate.

## Linked issue

Closes CLI-2857

5591 of 12006 relevant lines covered (46.57%)

25.05 hits per line

Jobs
ID Job ID Ran Files Coverage
1 40522106715.1 27 Oct 2026 02:33PM UTC 119
46.57
GitHub Action Run
Source Files on build 40522106715
  • 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 #40522106715
  • 3507dba6 on github
  • Prev Build on gh-readonly-queue/develop/pr-7347-11559a9d37d5f26e8682a9d85df0d6119e6bed29 (#40521826005)
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