Skip to content

chore: production deploy - #6416

Merged
supabase-cli-releaser[bot] merged 97 commits into
mainfrom
develop
Sep 7, 2026
Merged

chore: production deploy#6416
supabase-cli-releaser[bot] merged 97 commits into
mainfrom
develop

Conversation

@supabase-cli-releaser

@supabase-cli-releaser supabase-cli-releaser Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

johnstonmatt and others added 30 commits August 26, 2026 20:17
@johnstonmatt @kanadgupta
feat(cli): add supabase workers new (#6261)
b4a9199 
## Summary

Adds `supabase workers new`, plus the project layout and `config.toml`
editing the
whole command family builds on:

- `shared/workers/` — worker path resolution, `config.toml` section
reading and
patching (`toml-section.ts` preserves surrounding formatting), the
runtime/size
  envelope, and the starter files.
- Starter files live as ordinary files under
`shared/workers/stacks/<runtime>/`
rather than string literals, and are embedded into the compiled binary
through a
  Bun macro — the directory is expanded at transpile time and inlined.
A completeness check inside the macro fails the build if
`WORKER_RUNTIMES` and
  the directory drift apart.

**Stack 2 of 4**, on top of the config schema (#6260).

Reviewer note: the third commit is where the embedding mechanism is
explained; the
starters are deliberately kept out of the type program (a `deno` starter
is not
valid under this workspace's Bun types), which is why `tsconfig.json`
excludes the
directory and nothing imports the files.

## Linked issue

FUNC-753 (Linear). Supabase maintainer, exempt from the
`open-for-contribution` flow.

## Checklist

- [x] The PR title follows [Conventional
Commits](https://www.conventionalcommits.org/)

---------

Co-authored-by: Kanad Gupta <git@kanad.dev>
@johnstonmatt
feat(cli): add supabase workers push (#6262)
4214807 
## Summary

Adds `supabase workers push` (aliased `deploy`) and the machinery it
needs:

- `workers-api.ts` — the typed Workers Management API client.
- `tar.ts` / `worker-package.ts` — packaging a worker directory into the
build
  context that gets uploaded.
- `worker-classify.ts` — best-effort runtime detection from marker
files, so a
directory with no `[workers.<name>] runtime` can still deploy. The guess
is
  always reported with a nudge to pin it down, never applied silently.

**Stack 3 of 4**, on top of `workers new` (#6261).

## Linked issue

FUNC-753 (Linear). Supabase maintainer, exempt from the
`open-for-contribution` flow.

## Checklist

- [x] The PR title follows [Conventional
Commits](https://www.conventionalcommits.org/)
@dependabot
chore(deps): bump the go-minor group across 2 directories with 1 upda…
1cbf960 
…te (#6350)

Bumps the go-minor group with 1 update in the /apps/cli-go directory:
[google.golang.org/grpc](https://github.com/grpc/grpc-go).
Bumps the go-minor group with 1 update in the /apps/cli-go/pkg
directory: [google.golang.org/grpc](https://github.com/grpc/grpc-go).

Updates `google.golang.org/grpc` from 1.83.0 to 1.83.1
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/grpc/grpc-go/releases">google.golang.org/grpc's
releases</a>.</em></p>
<blockquote>
<h2>Release 1.83.1</h2>
<h1>Security</h1>
<ul>
<li>xds/rbac: Fix a bug where nested <code>Principal</code> or
<code>Permission</code> rules with <code>:scheme</code> or
<code>grpc-</code> prefixed header matchers were not rejected, which
could cause DENY rules to fail open. (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9258">#9258</a>)
<ul>
<li>Special Thanks: <a
href="https://github.com/nvxbug"><code>@​nvxbug</code></a></li>
</ul>
</li>
<li>xds/rbac: Fix a bug where the <code>host</code> header matcher was
not being replaced with <code>:authority</code> in nested
<code>Principal</code> or <code>Permission</code> rules. (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9258">#9258</a>)
<ul>
<li>Special Thanks: <a
href="https://github.com/nvxbug"><code>@​nvxbug</code></a></li>
</ul>
</li>
<li>xds/rbac: Fix a bug where a header matcher whose name was not
lowercase, such as <code>X-Role</code>, matched no header, which could
cause DENY rules to fail open. (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9332">#9332</a>)
<ul>
<li>Special Thanks: <a
href="https://github.com/alimony"><code>@​alimony</code></a></li>
</ul>
</li>
<li>xds/rbac: Fix a bug where a <code>:scheme</code> or
<code>grpc-</code> prefixed header matcher was accepted when its name
was not lowercase. (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9332">#9332</a>)
<ul>
<li>Special Thanks: <a
href="https://github.com/alimony"><code>@​alimony</code></a></li>
</ul>
</li>
<li>xds/rbac: Fix a bug where a <code>Host</code> header matcher was not
replaced with <code>:authority</code>. (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9332">#9332</a>)
<ul>
<li>Special Thanks: <a
href="https://github.com/alimony"><code>@​alimony</code></a></li>
</ul>
</li>
</ul>
<h1>Performance</h1>
<ul>
<li>transport: Restrict memory overhead of buffering small data frames.
(<a
href="https://redirect.github.com/grpc/grpc-go/issues/9331">#9331</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/grpc/grpc-go/commit/1550d9e0cddb30ce99e61a2102e8294a49461e5e"><code>1550d9e</code></a>
Change version to 1.83.1 (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9336">#9336</a>)</li>
<li><a
href="https://github.com/grpc/grpc-go/commit/ebba6f3f1b206e2b4dc4d1d5a96d18430302c2fe"><code>ebba6f3</code></a>
Cherry-pick <a
href="https://redirect.github.com/grpc/grpc-go/issues/9258">#9258</a>
and <a
href="https://redirect.github.com/grpc/grpc-go/issues/9332">#9332</a>
into v1.83.x (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9335">#9335</a>)</li>
<li><a
href="https://github.com/grpc/grpc-go/commit/8cfeca0e1ee5ea0980dcc320e20240fa1079ec77"><code>8cfeca0</code></a>
Cherry-pick <a
href="https://redirect.github.com/grpc/grpc-go/issues/9331">#9331</a> to
v1.83.x (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9333">#9333</a>)</li>
<li><a
href="https://github.com/grpc/grpc-go/commit/dec6951305e88906696f1d0a00dd2439363bc708"><code>dec6951</code></a>
Change version to 1.83.1-dev (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9229">#9229</a>)</li>
<li>See full diff in <a
href="https://github.com/grpc/grpc-go/compare/v1.83.0...v1.83.1">compare
view</a></li>
</ul>
</details>
<br />

Updates `google.golang.org/grpc` from 1.83.0 to 1.83.1
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/grpc/grpc-go/releases">google.golang.org/grpc's
releases</a>.</em></p>
<blockquote>
<h2>Release 1.83.1</h2>
<h1>Security</h1>
<ul>
<li>xds/rbac: Fix a bug where nested <code>Principal</code> or
<code>Permission</code> rules with <code>:scheme</code> or
<code>grpc-</code> prefixed header matchers were not rejected, which
could cause DENY rules to fail open. (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9258">#9258</a>)
<ul>
<li>Special Thanks: <a
href="https://github.com/nvxbug"><code>@​nvxbug</code></a></li>
</ul>
</li>
<li>xds/rbac: Fix a bug where the <code>host</code> header matcher was
not being replaced with <code>:authority</code> in nested
<code>Principal</code> or <code>Permission</code> rules. (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9258">#9258</a>)
<ul>
<li>Special Thanks: <a
href="https://github.com/nvxbug"><code>@​nvxbug</code></a></li>
</ul>
</li>
<li>xds/rbac: Fix a bug where a header matcher whose name was not
lowercase, such as <code>X-Role</code>, matched no header, which could
cause DENY rules to fail open. (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9332">#9332</a>)
<ul>
<li>Special Thanks: <a
href="https://github.com/alimony"><code>@​alimony</code></a></li>
</ul>
</li>
<li>xds/rbac: Fix a bug where a <code>:scheme</code> or
<code>grpc-</code> prefixed header matcher was accepted when its name
was not lowercase. (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9332">#9332</a>)
<ul>
<li>Special Thanks: <a
href="https://github.com/alimony"><code>@​alimony</code></a></li>
</ul>
</li>
<li>xds/rbac: Fix a bug where a <code>Host</code> header matcher was not
replaced with <code>:authority</code>. (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9332">#9332</a>)
<ul>
<li>Special Thanks: <a
href="https://github.com/alimony"><code>@​alimony</code></a></li>
</ul>
</li>
</ul>
<h1>Performance</h1>
<ul>
<li>transport: Restrict memory overhead of buffering small data frames.
(<a
href="https://redirect.github.com/grpc/grpc-go/issues/9331">#9331</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/grpc/grpc-go/commit/1550d9e0cddb30ce99e61a2102e8294a49461e5e"><code>1550d9e</code></a>
Change version to 1.83.1 (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9336">#9336</a>)</li>
<li><a
href="https://github.com/grpc/grpc-go/commit/ebba6f3f1b206e2b4dc4d1d5a96d18430302c2fe"><code>ebba6f3</code></a>
Cherry-pick <a
href="https://redirect.github.com/grpc/grpc-go/issues/9258">#9258</a>
and <a
href="https://redirect.github.com/grpc/grpc-go/issues/9332">#9332</a>
into v1.83.x (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9335">#9335</a>)</li>
<li><a
href="https://github.com/grpc/grpc-go/commit/8cfeca0e1ee5ea0980dcc320e20240fa1079ec77"><code>8cfeca0</code></a>
Cherry-pick <a
href="https://redirect.github.com/grpc/grpc-go/issues/9331">#9331</a> to
v1.83.x (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9333">#9333</a>)</li>
<li><a
href="https://github.com/grpc/grpc-go/commit/dec6951305e88906696f1d0a00dd2439363bc708"><code>dec6951</code></a>
Change version to 1.83.1-dev (<a
href="https://redirect.github.com/grpc/grpc-go/issues/9229">#9229</a>)</li>
<li>See full diff in <a
href="https://github.com/grpc/grpc-go/compare/v1.83.0...v1.83.1">compare
view</a></li>
</ul>
</details>
<br />


Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@supabase-cli-releaser
chore: sync API types from infrastructure (#6352)
80bfa50 
This PR was automatically created to sync API types from the
infrastructure repository.

Changes were detected in the generated API code after syncing with the
latest spec from infrastructure.

Co-authored-by: supabase-cli-releaser[bot] <246109035+supabase-cli-releaser[bot]@users.noreply.github.com>
@jgoux
feat(stack): replace remote runtime protocol with Effect RPC (#6303)
ca8b80f 
## Summary

- Replace the runtime REST and SSE daemon protocol with a static control
plane exposing owner discovery, session-fenced shutdown, and
same-version Effect RPC over HTTP and NDJSON.
- Use the immutable, unique CLI version as the sole runtime
compatibility identity; source execution uses the explicit 0.0.0-dev
development sentinel.
- Make an incompatible CLI version an explicit parent-owned full stack
stop/start authorized only by supabase start; connect-only and ordinary
child paths report the typed upgrade requirement without restarting the
live owner.
- Preserve managed data, document and launch metadata, runtime
selection, pinned service versions, raw exclusions, and sticky ports
across the upgrade restart.
- Serialize startup, runtime scope ownership, terminal persistence, and
shutdown through one Effect Queue-backed SupervisorSession actor,
releasing the control listener last across Node, Bun, and compiled Bun
runtimes.
- Update CLI consumers, error reporting, integration helpers, targeted
process coverage, and durable architecture documentation for the
single-protocol cutover.

## Linked issue

None.

## Reviewer context

This intentionally has no legacy protocol window, compatibility adapter,
adoption path, or in-place supervisor swap. Runtime RPC is a
same-version boundary; owner discovery and session-fenced shutdown
remain the stable cross-build protocol. Upgrading through supabase start
restarts the complete stack, so active application connections and
tooling streams disconnect briefly while durable state and launch
selections remain intact.
@jgoux
chore(repo): remove Nx (#6344)
e6710aa 
## Summary

- remove the remaining Nx configuration, package metadata, inference
plugin workspace, dependencies, cache ignores, and lockfile graph
- update current contributor guidance to use package scripts and
root-owned Turbo tasks for execution and dependency inspection
- preserve the build, generation, quality, live, auxiliary, and test
graphs established by the preceding Turborepo migrations

## Context

PR #6343 merged while this change was in progress, so this branch was
rebased onto the updated `develop` branch containing its final live and
auxiliary task migration. Task execution is now owned entirely by
package scripts and Turbo.

Affected execution, persistent cache storage, and remote caching remain
separate follow-up optimizations.
@supabase-cli-releaser @jgoux
chore(api): sync Management API OpenAPI spec (#6338)
4c9986d 
This PR was automatically created to sync the generated `@supabase/api`
package with the latest Management API OpenAPI document.

Changes were detected in the upstream OpenAPI documents exposed by
`https://api.supabase.com/api/v1-json` and
`https://api.supabase.com/api/v2-json`.

Co-authored-by: jgoux <1443499+jgoux@users.noreply.github.com>
@dependabot @github-actions @jgoux
fix(docker): bump the docker-minor group across 1 directory with 5 up…
ab54bd0 
…dates (#6320)

Bumps the docker-minor group with 5 updates in the
/apps/cli-go/pkg/config/templates directory:

| Package | From | To |
| --- | --- | --- |
| postgrest/postgrest | `v16.1` | `v16.2` |
| supabase/studio | `2026.08.17-sha-0c1da8f` | `2026.08.24-sha-8ec45b2`
|
| supabase/realtime | `v2.129.3` | `v2.129.9` |
| supabase/storage-api | `v1.70.3` | `v1.71.0` |
| supabase/logflare | `1.50.4` | `1.50.6` |


Updates `postgrest/postgrest` from v16.1 to v16.2

Updates `supabase/studio` from 2026.08.17-sha-0c1da8f to
2026.08.24-sha-8ec45b2

Updates `supabase/realtime` from v2.129.3 to v2.129.9

Updates `supabase/storage-api` from v1.70.3 to v1.71.0

Updates `supabase/logflare` from 1.50.4 to 1.50.6


Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions


</details>

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Julien Goux <hi@jgoux.dev>
@supabase-cli-releaser @jgoux
chore(api): sync Management API OpenAPI spec (#6356)
0465010 
This PR was automatically created to sync the generated `@supabase/api`
package with the latest Management API OpenAPI document.

Changes were detected in the upstream OpenAPI documents exposed by
`https://api.supabase.com/api/v1-json` and
`https://api.supabase.com/api/v2-json`.

Co-authored-by: jgoux <1443499+jgoux@users.noreply.github.com>
@supabase-cli-releaser
chore: sync API types from infrastructure (#6359)
c07d4de 
This PR was automatically created to sync API types from the
infrastructure repository.

Changes were detected in the generated API code after syncing with the
latest spec from infrastructure.

Co-authored-by: supabase-cli-releaser[bot] <246109035+supabase-cli-releaser[bot]@users.noreply.github.com>
@Coly010
chore(release): harden release-notes prompt against injection (#6361)
62f76bc 
## Summary

Defense-in-depth hardening for the automated release-notes generator
(`propose-release-notes.yml` →
`apps/cli/scripts/propose-release-notes.ts`), which runs the Claude
Agent SDK with `Bash` + `WebFetch`/`WebSearch` and feeds it the
semantic-release changelog block (built from contributor commit subjects
/ PR titles) plus PR bodies and linked issues it fetches at runtime —
all attacker-influenceable content, previously with no injection guard.

This PR adds an explicit **trust boundary** to
`tools/release/release-notes-prompt.md`:

- A top-of-file section establishing that the changelog block and all
fetched PR/issue/web content are **untrusted data to be summarized,
never instructions to obey**.
- Rules that override embedded instructions: don't act on injected
commands; never disclose env vars / secrets / tokens; restrict `Bash` to
read-only `gh` GETs on `supabase/cli`; restrict `WebFetch`/`WebSearch`
to `github.com/supabase/cli`; produce only the release-notes markdown.
- Inline reminders at the two points where untrusted content enters (the
changelog block and the PR-investigation step).

The `{{PASTE_SEMANTIC_RELEASE_BLOCK_HERE}}` placeholder is unchanged, so
the generator's template check and output contract are unaffected.

## Scope / follow-up

This is **defense-in-depth only** — prompt guards are best-effort
against a determined injection. The stronger, structural containment is
deliberately **left for a follow-up**:

1. Separate the write-capable GitHub App token (`GH_TOKEN`,
`contents`/`pull-requests: write` on the protected default branch) from
the agent's process — generate notes in an agent-only step with no GH
token, then push/open the PR in a separate step that runs no model.
2. Drop `Bash` (and ideally `WebFetch`) from the agent's `allowedTools`,
pre-fetching the PR/issue data with trusted code instead — removing the
shell/network exfiltration primitive.

Context: surfaced during the security review of the AI-review pipeline
(#6358); the release-notes workflow shares the "untrusted content +
secrets in an agentic CI job" class of exposure, gated behind a
maintainer-cut stable release rather than per-PR.
@Coly010
feat(config): add toProjectConfig and the ProjectConfig hosted subset…
c3064f1 
… (CLI-2230) (#6339)

## What changed

Implements
[CLI-2230](https://linear.app/supabase/issue/CLI-2230/create-a-toprojectconfig-function-that-is-exported-from-the-config):
the hosted-project subset type `ProjectConfig` and its normalizers,
exported from `@supabase/config`'s pure (browser-safe) entrypoint so the
CLI and Studio share one mapper.

- **`fromConfigDocument(config)`** — projection of a `CliConfig`
document (or any `EffectiveConfig`) down to the hosted sections (`api`,
`auth`, `db`, `realtime`, `storage`, `workers`, `experimental`).
- **`fromApiProjectConfig(input)`** — translation of a Management API v2
project-config response (full envelope, `data` object, or bare
`data.attributes`). Registry-driven: 233 mapping rows mined from the
legacy `config push` sync mappers (`config-sync/*.sync.ts`), covering
renames (`rate_limit_otp` → `sign_in_sign_ups`), boolean inversions
(`disable_signup`, `mailer_autoconfirm`), unit conversions
(seconds/hours → Go duration strings, int64 bytes → BytesSize), the
GoTrue key table (19 OAuth providers, 6 hooks, 5 SMS providers), and
`x-secret` omission (the API only reports HMAC digests). Decode is
lenient per ADR 0019 — unknown/API-ahead keys never fail; the raw
attributes ride along as a **non-enumerable `_apiResponse`** (invisible
to encodes, spreads, and structural walks; never persisted), with a
registry-derived `unmappedApiFields()` reader.
- **`toProjectConfig(source)`** — thin dispatcher over both (`{
cliConfig }` / `{ apiResponse }`).

### Operand widening (ruling on CLI-2230)

`ProjectConfig` is deliberately **sparse** — an API response never
mentions sections it doesn't manage, and flooding in schema defaults
would fabricate drift. To make it a first-class operand of the
comparison core, `BaseCliConfig` is replaced by the family-neutral
`EffectiveConfig = DeepPartial<Omit<CliConfig, "remotes">>` on
`subtractCliConfig`/`omitDefaultValues`. No runtime change — the
subtraction walk already had the right absence semantics. Recorded in
ADR 0018's 2026-08-26 addendum; the naming-rule generalization lands
separately with CLI-2238 (#6335).

### apps/cli

- A type-drift guard (`project-config-api-drift.unit.test.ts`) pins the
generated `V2GetProjectConfigOutput` attributes against the package's
lenient input schema: assignability (catches type widening) plus
per-section key-set assertions (catch added/removed/renamed fields) — so
OpenAPI drift fails compile before it can silently break the mapping. No
runtime dependency on `packages/api` was added.
- `ProjectConfigParseError` registered in the error-actionability table
as `apiStatus` (a malformed platform response, not a user config
mistake).

### Reviewer notes

- Deliberate divergences from the legacy apply semantics are documented
inline where they occur: API `null` → omit (sparse output has no local
document to fall back to), `uri_allow_list` trimming, `smtp_host: ""`
treated as disabled, `sms_autoconfirm` **not** inverted (matches
`auth.sync.ts:1677/:2485` — only the mailer counterpart inverts).
- An explicit `db_schema: ""` maps to `{ api: { enabled: false } }`
only, mirroring `applyRemoteApiConfig`'s early return; an *absent*
`db_schema` doesn't gate the sibling fields.
- Follow-up candidate deliberately not in this PR: a parity test pinning
the replicated legacy helpers
(duration/BytesSize/parseUint16/envToMap/password charsets) against
their `apps/cli` originals. (ADR 0019's attach helper *did* land in the
second round below, as `attachApiResponse`.)

### Second review round (commit 93b4679) — adjudication record

A two-set review (architect/engineer/security/DX + adversarial
execution) ran against bdd607f. The registry mapping itself survived
three independent verification passes with zero defects; every accepted
finding about the surrounding surface is fixed in 93b4679:

- **Secrets**: `fromConfigDocument` now deep-copies and omits every
`x-secret` leaf (schema-derived, `lib/secret-paths.ts`) — decoded
documents hold plaintext credentials, and the subtract composition
rendered them as drift.
- **Spelling convergence**: new registry `normalizeDocument` column
canonicalizes document-side duration and byte-size spellings so both
normalizers emit one form for one logical value.
- **Leniency**: the mirror schema types every never-mapped field
`Schema.Unknown`, so a platform type change on a field nothing reads can
no longer fail every decode.
- **Errors**: `ProjectConfigParseError` gained
`message`/`detail`/`suggestion` (upgrade-then-report), schema-issue
paths lift into `apiPath`, telemetry adds `fingerprint_suffix:
"api_response"` + `has_suggestion`.
- **Type-mismatch unification**: string rows, `smtp_host`/`smtp_port`,
and CIDR entries now throw typed errors instead of fabricating values
(`enabled: false`), vanishing silently, or partially filtering a
security allowlist; `expectNumber` rejects non-finite.
- **`_apiResponse`**: cloned + deep-frozen at attach (no caller
aliasing); `attachApiResponse` export restores it across spread/clone
round-trips; invisibility claim narrowed (serializers and walks — debug
inspectors like Bun's `console.log` still print it; never log an
API-sourced config).
- **`unmappedApiFields`**: recursion depth cap; `unmappedSecretApiPaths`
deny list (`external_figma_secret` — the one genuine orphan digest; the
review's other two candidates don't exist in the legacy source).
- **New guards/exports**: `registry-integrity.unit.test.ts` (all 233
rows' paths resolve against the schema ASTs, 470 generated cases);
drift-guard key-set levels completed;
`comparableProjectConfigPaths`/`isComparableProjectConfigPath` so diff
consumers never hand-maintain field lists; `inverse` implementations
dropped until the push mapper derives them.

**Explicit rejections** (reviewed, not silently deferred):
1. *`alsoConsumes` static consumed-set*: "consumed" means
known-to-this-registry-version, not mapped-on-this-run — an
`alsoConsumes` sibling whose anchor didn't run stays suppressed by
design and remains in `_apiResponse`. Documented in `walkUnmapped`.
2. *WeakMap sidecar for `_apiResponse`*: deferred — clone+freeze
resolves the aliasing hazard and the narrowed docstring is honest;
revisit if CLI-2156 consumption shows inspectors bite (ADR 0019 records
the alternative).
3. *`fromCliConfig`/`fromApiResponse` renaming*: the shipped names are
already recorded in ADR 0020 (#6335), Linear, and coordinated docs —
symmetry isn't worth re-coordinating three artifacts.
4. *Branding `EffectiveConfig`*: took the ADR 0018 consequence note
instead (widening removes the static every-section guarantee; callers
own operand completeness).
5. *`ProjectConfigApiAttributes` placement* and *`"sideEffects":
false`*: deferred to their owning issues with notes filed — CLI-2234
(export-surface audit) and CLI-2232 (verify the bundler claim against a
built artifact).

### Verification round (commits 5f389c9 + 0424ac7)

An executed verification pass over 93b4679 re-ran all prior attacks
(10/10 now pass) and surfaced residuals, fixed in 0424ac7:

- **Orphan digests were 3, not 1** — the generated
`V1GetAuthServiceConfigOutput` contract (not the legacy interface) is
the authority; `external_slack_secret`,
`hook_after_user_created_secrets`, and `nimbus_oauth_client_secret` join
the deny list, and a new apps/cli **contract-guard test** cross-checks
every auth apiPath + secret-suffixed contract key against the registry
(also closing the open-Record vacuity in the integrity test's auth
checks). Registry rows are now exported from the package root to serve
it.
- **Clone/freeze regression fixed**: deep/cyclic/non-cloneable payloads
now throw `ProjectConfigParseError` instead of raw
`RangeError`/`DOMException` (depth-capped pre-walk, wrapped clone,
cycle-guarded `deepFreeze`).
- **README example rewritten and executed** (the previous snippet
self-subtracted and filtered section names — always empty);
secret-stripped projections prune emptied containers; a real
phantom-drift pin replaces an agreeing-case test;
`comparableProjectConfigPaths`' docstring narrowed to the section-level
claim it delivers; ADR 0019 gained a dated addendum (attach helper,
structural "verbatim", debug-inspector caveat).
- **Documented-not-changed**: byte-size canonicalization quantizes at 4
significant digits symmetrically on both arms — sub-0.1% differences
comparing equal is a deliberate property (user-authored spellings are
exact).

The merge commit resolves the pre-agreed README conflict with #6335
(their `## Naming` section wins, its "in flight" sentence flipped) and
de-stales ADR 0020's phrasing, per the coordinated rebase checklist.
Known external: root `check:all` fails on `@supabase/cli-go#lint:check`
(5 gosec findings in Go files byte-identical to develop —
develop-side/toolchain, not this PR).

### Drift-audit round (commit 492ee25)

A 2026-08-27 audit compared the post-codex state against CLI-2230's
design intent. All eight structural commitments verified intact (pure
entrypoint, no `packages/api` dependency, sparse output +
`EffectiveConfig`, ADR 0019 guardrails, registry-driven with `inverse`
unimplemented, purity graph, naming, secret stripping). Three executed
repros surfaced semantic drift introduced by the codex rounds; fixed
here:

- **Leniency**: `JSON.parse('{"x":1e400}')` yields `Infinity`, so the
round-12 non-finite pre-decode rejection hard-failed a real JSON payload
on an *unknown* field (mis-bucketed as `caller_misuse`). The walk now
rejects only bigint/`undefined`/`NaN` (values `JSON.parse` cannot
produce); non-finite values decode and surface as `null` from
`unmappedApiFields` (scalars and inside array leaves, identity preserved
for all-finite arrays). ADR 0019 gains a dated leniency-boundary
addendum.
- **SMTP absence semantics**: an absent `smtp_host` previously counted
as the disabled sentinel, silently dropping
`smtp_user`/`smtp_admin_email`/`rate_limit.email_sent` from both the
output and `unmappedApiFields` — contradicting the SMS
absent-vs-sentinel rule beside it. Absence now says nothing; only the
explicit `""`/`null` legacy sentinel disables (three-state, extended to
the `email_sent` cross-section rule).
- **Convergence-predictor ruling (ADR 0021)**: the codex rounds had
incrementally turned both normalizers into *post-push convergence
predictors* (SMS provider precedence flips extra enabled providers,
disabled-sentinel pruning, `null`-gated booleans, CSV/uint/duration
canonicalization) — defensible (it kills phantom drift for CLI-2156) but
never adjudicated or documented. Ruling: **accepted**, now recorded in
ADR 0021, the
`ProjectConfig`/`fromConfigDocument`/`fromApiProjectConfig` docstrings,
and the README ("not a verbatim representation" caveat).
- **Guards**: the three hand-written sentinel/precedence tables
(`DISABLED_SENTINEL_PRUNES`, `DISABLED_SENTINEL_ENTRY_SWEEPS`,
`SMS_PROVIDER_PUSH_PRECEDENCE`) now resolve every path/key against the
schema ASTs in `registry-integrity` — previously a schema rename
silently no-opped them — and the SMS precedence order is pinned against
the legacy push switch (`auth.sync.ts:2498-2539`).
- Residual cleanups: the stale `Math.trunc` comment above the fraction
arithmetic (round-11/14 artifact the round-20 revert missed),
`ReadonlyJsonValue` exported (it appears in public types),
`smtpExplicitlyDisabledInAttributes` simplified to mirror
`smsProviderExplicitlyUnset`, ADR index gains 0020/0021.

An engineer-review pass over the fix diff verified every change; its
findings (the `email_sent` asymmetry, stale ADR citations, formatter
gate, doc phrasing) are folded in. 984/984 package tests, 461/461
apps/cli guard tests, typechecks clean both packages.

Follow-ups filed so they survive CLI-2230 closing:
[CLI-2266](https://linear.app/supabase/issue/CLI-2266/derive-the-config-push-mapper-from-the-projectconfig-mapping-registry)
(registry-derived push mapper — carries the three requirements
previously parked as CLI-2230 comments) and
[CLI-2267](https://linear.app/supabase/issue/CLI-2267/pin-supabaseconfigs-replicated-legacy-parsers-with-parity-fixtures-in)
(parity fixtures pinning the replicated legacy parsers against
`config-sync/*`).

Fixes CLI-2230

🤖 Generated with [Claude Code](https://claude.com/claude-code)
@Coly010
ci(repo): add one-shot two-model AI review pipeline (#6358)
fae5d93 
## Summary

Replaces the Codex GitHub App's per-push auto-review churn (often 30–40
short rounds per PR) with an in-repo pipeline that reviews each PR
**exactly once**, unless a maintainer explicitly re-runs it.

**Pipeline** (`.github/workflows/ai-review.yml`; full design + security
model in `.github/ai-review/README.md`):

1. **resolve** — decides whether to run: once-per-PR dedup (bot-authored
marker), draft/bot/fork skips for auto triggers, `/ai-review`
authorization (requires repo **write/admin** via effective-permission
lookup), diff-size guard. Runs only trusted default-branch code.
2. **claude-review** — Claude Code headless (`claude-fable-5`), one
exhaustive pass, read-only tools, JSON validated against
`findings.schema.json`.
3. **codex-review** — `openai/codex-action` (`gpt-5.6-sol`, drop-sudo +
read-only sandbox): independent review **plus** adjudication of every
Claude finding (confirmed / refuted-with-evidence / uncertain), merged
into `merged-review.schema.json`.
4. **post-review** — deterministic Bun script posts **one** consolidated
PR review (`COMMENT`, advisory only): inline comments for anchorable
findings, refuted findings preserved in a collapsed section (never
silently dropped), verdict counts computed locally (not trusted from the
model). Re-runs supersede the prior review.

**Once-per-PR**: no `synchronize` trigger, bot-authored marker dedup,
per-PR concurrency (non-command comments can't cancel an in-flight run).
Re-run only via `/ai-review` (maintainers) or `workflow_dispatch`.

## Security model

This ran through security + engineering review (twice). A critical
secret-exfiltration path was found and closed; the design now enforces:

- **Model jobs never execute PR-authored code.** The PR head is checked
out only as read-only review subject matter (`claude` reads it with
Read/Grep/Glob under `--bare`/`--strict-mcp-config`); every executed
file — prompts, schemas, the validator script — comes from a separate
trusted default-branch checkout, and no `bun` process ever runs with a
cwd inside the PR checkout (so a PR-authored `bunfig.toml`/`.env` can't
preload code). npm installs are config-isolated and version-pinned;
Codex reviews from `/tmp` with no PR checkout at all.
- **Least privilege**: top-level `permissions: {}`; model jobs hold no
write scope; the only write-capable job (`post-review`) runs base-branch
code exclusively. All actions SHA-pinned.
- **Output is scrubbed**: model-provided text is sanitized
(mentions/refs/HTML neutralized, `file` field guarded against markdown
breakout) and secret-pattern-redacted before it's posted or uploaded as
an artifact (defense-in-depth; a dedicated rotatable key is the real
containment — see README).
- Advisory-only (`COMMENT`), never a required check, never runs in the
merge queue.

## Rollout (shadow mode)

The `pull_request` trigger ships **commented out**. Plan: add a
dedicated `OPENAI_API_KEY` secret (and ideally a dedicated
`ANTHROPIC_API_KEY` rather than the shared release-notes key), tune
prompts against real PRs via `workflow_dispatch`, then enable the
trigger and switch the Codex app to manual-only simultaneously. Steps +
caveats in the README.

## Notes for reviewers

- New `.github/workflows/github-scripts-ci.yml` finally runs the
`.github/scripts` test suites + type-check in CI (they ran nowhere
before — this also covers the pre-existing `contribution-gate` tests).
- Requires a new `OPENAI_API_KEY` repo secret; `ANTHROPIC_API_KEY`
already exists.
@Coly010
ci(repo): fix ai-review gh repo inference and scripts-ci timeout (#6363)
4080771 
Two CI fixes for the AI-review pipeline (#6358), both surfaced
immediately after merge.

## 1. `Claude review` job fails at "Fetch PR diff and metadata"

The first live `/ai-review` run failed with `fatal: not a git
repository`. The `claude-review` job checks out into **subdirectories**
(`pr/` for the PR head, `trusted/` for the base), so `$GITHUB_WORKSPACE`
itself isn't a git repo — and `gh pr diff`/`gh pr view` infer the repo
from the current directory's git remote. Fix: pass `--repo
"$GITHUB_REPOSITORY"` explicitly at both `gh` call sites (claude-review
and, defensively, codex-review) so `gh` never depends on cwd.

## 2. `Test and type-check` (github-scripts-ci) times out

The shared `./.github/actions/setup` installs the full workspace + Go
toolchain via mise (~9–10 min), which raced the job's `timeout-minutes:
10` and got cancelled on a cold cache (the setup step never finished;
tests/type-check never ran). Raised to 20 min. Noted inline that the
check is heavier than it needs to be for two scripts — slimming the
setup is a possible follow-up.
@johnstonmatt
feat(cli): add supabase workers list, status and delete (#6263)
f3d1e6b 
## Summary

Completes the command family with the three remaining subcommands:

- `workers list` — this project's workers.
- `workers status` — one worker in detail.
- `workers delete` — remove a worker, with confirmation.

All three reuse the API client and output helpers introduced in #6262,
so this is
the smallest layer of the stack.

**Stack 4 of 4**, on top of `workers push` (#6262).

## Linked issue

FUNC-753 (Linear). Supabase maintainer, exempt from the
`open-for-contribution` flow.

## Checklist

- [x] The PR title follows [Conventional
Commits](https://www.conventionalcommits.org/)
@jgoux
chore(lint): scope Effect checks to stack packages (#6357)
7cbea8e 
## Summary

Set up Effect-aware Oxlint for `packages/stack` and
`packages/process-compose` using the Effect-recommended Oxlint preset
and TypeScript plugin. The scoped check is wired into the monorepo task
graph and denies warnings, matching the global Oxlint policy. The
generic pass excludes these two packages while the scoped config extends
the generic ruleset, so generic and Effect rules each run exactly once
without bringing Effect lint into `apps/cli`.

Remediate the existing scoped diagnostics in reviewable waves: typed
Effect failures and schema decoding, reusable Effect and Stream service
values, lifecycle-safe transport cleanup, and focused test-boundary
cleanup. Persisted managed-stack documents and identity markers now
encode through the same schemas used to read them. The merged #6303
transport architecture remains authoritative. Exact `apps/cli` callsites
were updated where the stack Effect service API changed, but CLI code is
intentionally not an Effect-lint target yet.

Native Node, Bun, Deno, and Promise boundaries retain narrow documented
suppressions where replacing the host API or dependency-ordered layer
provisioning would worsen lifecycle semantics.

Supersedes #6304
@supabase-cli-releaser
chore: sync API types from infrastructure (#6373)
c8fc1d6 
This PR was automatically created to sync API types from the
infrastructure repository.

Changes were detected in the generated API code after syncing with the
latest spec from infrastructure.

Co-authored-by: supabase-cli-releaser[bot] <246109035+supabase-cli-releaser[bot]@users.noreply.github.com>
@Coly010 @jgoux
ci(repo): parallel AI review passes with a Codex adjudicator, no size…
de26a30 
… cap (#6365)

Refines the AI review pipeline (built in #6358) into its intended shape,
and removes the size limit. Validated end-to-end via a temporary
self-test trigger during development (now removed — the pipeline ships
in shadow mode).

## What changed

- **Parallel independent reviews + a dedicated adjudicator.**
`claude-review` and `codex-review` now run **in parallel** (Codex no
longer depends on Claude); a new **`adjudicate`** job then reconciles
both finding sets, verifying each finding by **reading the real code**
(PR head checked out read-only), and `post-review` posts the merged
result. This replaces the old single Codex job that did both an
independent pass and adjudication sequentially — cutting the critical
path and giving each job its own timeout.
- **No size cap.** Removed the preemptive "too large" guard. The models
review agentically (reading the diff and files via their own tools over
many turns, like the local CLI), so PRs of any size are reviewed — very
large diffs best-effort within the model's context/turn budget.
- **Runtime fixes** surfaced by real runs: `gh pr diff --repo` (subdir
checkouts), npm config isolation for the Claude CLI install, `set +e` so
the Claude retry loop isn't killed by `bash -e`, and the reviewer model
set to `claude-opus-5` (the account's API key returns 404 for
`claude-fable-5`).

Workflow + prompts only for the split (no TS/schema changes — Codex's
independent findings reuse `findings.schema.json`; the adjudicator still
emits `merged-review.json`). Ships in **shadow mode**: no `pull_request`
trigger, only `workflow_dispatch` / maintainer `/ai-review`.

## Notes for reviewers

- Two first-run unknowns for the adjudicator (can't verify offline):
whether Codex's read-only sandbox can read the `pr/` subtree, and
whether it picks up a nested `pr/AGENTS.md` (guarded in the prompt;
blast radius bounded — read-only + no network + key-proxied +
output-redacted).
- Requires the org's Anthropic/OpenAI spend limit to be sufficient, or
the model jobs 429.

---------

Co-authored-by: Julien Goux <hi@jgoux.dev>
@Coly010
ci(repo): fix codex-action v1.12 hang (downgrade to v1.11), adjudicat…
7a16903 
…e on >=1 review (#6380)

Follow-up to the AI-review pipeline. Two changes.

## 1. Downgrade `codex-action` v1.12 → v1.11

On the large PR (#6366, ~130k-token diff) the `codex-review` step ran to
completion — Codex finished the turn, wrote its output file, printed its
final message and token count — then **sat idle until the 45-minute job
timeout**, discarding a completed review. That is a confirmed v1.12
regression: **openai/codex-action#150** ("v1.12: Linux run never returns
after the turn completes; job dies on timeout with the output file
already written"). The reporter confirms **v1.11 handles the same heavy
workload cleanly**, and there is no released fix above v1.12.

v1.11 (`52fe01ec…`) supports every input we use (`safety-strategy`,
`sandbox`, `output-schema-file`, `output-file`, `codex-version`,
`working-directory`, `effort`), so this is a drop-in pin change in both
Codex jobs.

## 2. Adjudicate on ≥1 independent review (graceful degradation)

Previously `adjudicate` required BOTH `claude-review` and `codex-review`
to succeed, so one flaky model job sank the whole review. Now it runs
when **at least one** independent pass succeeded: each findings download
is guarded by its job's result, and the stage step substitutes an empty
findings set for any review that didn't complete, so the adjudicator
reconciles one or two. The prompt notes the one-review case and records
it in its summary.

Together: a Codex hiccup no longer wastes a 45-minute run or blocks
Claude's (working) review from being posted.
@jgoux
fix(stack): prepare slim postgres socket directory (#6401)
cbc4737 
## Summary

- prepare `/run/postgresql` for the Linux host UID/GID before the Docker
stack drops privileges
- preserve the existing root and non-Linux startup paths
- cover the privilege-drop ordering with a Linux-specific regression
test

## Context

The refreshed slim Postgres image listens on a Unix socket under
`/run/postgresql`. The stack wrapper bypassed the image root setup when
switching to the host user on Linux, so Postgres restarted with a socket
lock-file permission error. That readiness failure cascaded into the
three e2e startup timeouts visible on #6400.
@supabase-cli-releaser @avallete
chore: sync API types from infrastructure (#6399)
1e74dd9 
This PR was automatically created to sync API types from the
infrastructure repository.

Changes were detected in the generated API code after syncing with the
latest spec from infrastructure.

Co-authored-by: supabase-cli-releaser[bot] <246109035+supabase-cli-releaser[bot]@users.noreply.github.com>
Co-authored-by: Andrew Valleteau <avallete@users.noreply.github.com>
@jgoux
test(stack): qualify complete slim Docker service graph (#6374)
27d265c 
## Summary

- consolidate fragmented Docker coverage into one public 13-service
stack journey
- verify canonical slim images, representative product behavior, and
restart persistence
- prove two automatically allocated sibling stacks keep ports, data,
ownership, and cleanup isolated

## Context

This is a test-only qualification change for CLI-2113. The existing
stack implementation already satisfied the complete Docker graph and
sibling-isolation contracts; the new journey makes those
release-critical guarantees observable through the public package
surface.
@7ttp @avallete
fix(cli): accept sbp_v0 tokens (CLI-2262) (#6360)
e4cc29c 
## TL;DR

fixes the CLI rejecting dashboard issued `sbp_v0_` access tokens with
`LegacyInvalidAccessTokenError` which was caused by the access token
regex pattern only

matching the `sbp_` and `sbp_oauth_` prefixes and 
is now fixed by widening the legacy validator to also accept the
`sbp_v0_` prefix...

## ref:
- closes: #6348

---------

Co-authored-by: Andrew Valleteau <avallete@users.noreply.github.com>
@jgoux
test(stack): qualify native Postgres, Auth, and PostgREST core (#6379)
da117e8 
## Summary

Qualifies the first Dockerless native vertical slice through the public
`@supabase/stack` surface: isolated native prefetch, lazy and eager
activation, real Auth and PostgREST flows, PostgreSQL extensions,
restart preservation, retryable typed preparation failure, and exact
resource cleanup.

Adds a consumer-selected cache root to Promise-based prefetch, exposes
the public stack error type, and preserves lazy proxy activation across
a whole-stack restart without weakening explicit per-service stops.
@7ttp
fix(cli): stop skipping colliding schemas (CLI-2272) (#6394)
e2ee2a7 
## TL;DR

fixes `db reset, db lint, db diff`, and `migration down` silently
skipping a user schema when its oid also appears in another catalog
which was caused by joining `pg_depend` on objid without the `classid`
that scopes `oids` to a single catalog

now fixed by constraining the join to `pg_catalog.pg_namespace` rows in
every copy of the query.
Resets now drop schemas that earlier versions silently skipped....

## ref:
- closes: #6375
@pamelachia
docs(repo): add public-surfaces rule to agent instructions (#6400)
5c7156e 
Adds one sentence to the Pull Requests section of `AGENTS.md`: this repo
is public, so PR descriptions, issues, and code comments keep internal
content out: absolute production metrics (percentages, ratios, or
relative change instead), internal decision detail (vendor, legal,
pricing, or strategy discussions), and competitor names (protocol
identifiers such as user-agent strings are fine). That context goes in
the linked Linear issue. Same rule as the supabase monorepo's agent
instructions (supabase/supabase#49750); an agent-authored PR there had
quoted absolute internal event volumes in its description.
@7ttp
test(cli): cover services and storage mv (#6362)
68ade47 
## TL;DR

adds live e2e coverage for the `services` command and `storage mv`

## whats introduced?

- `services`: links the project and proves the postgres remote version
lands in the json output
proves the table renders that value in the LINKED cell, where a plain
substring match would pass vacuously
- `storage mv`: uploads an object, moves it through the real move
endpoint, and proves via the listing that the destination exists and the
source is gone
closes the storage family, since ls, cp and rm already have coverage
- `db pull`: deflakes the shipped live test, pull exits nonzero when
nothing changed by design, so the test now seeds remote-only schema
through db query and proves the initial pull writes it back as a
migration

## ref:
- closes: CLI-2263 CLI-2264 CLI-2278
@7ttp
test(cli): cover migration up and repair (CLI-2269) (#6376)
4a1f2de 
## TL;DR

adds live e2e coverage for `migration up` and `migration repair`,
closing the migration family...

## whats introduced?

- `migration up`: applies a test written migration to the remote
database, proven by the apply banner and the history row migration list
reads back
- `migration repair`: inserts a history row with status applied, proves
it through migration list, then removes it with status reverted and
proves the absence

## ref:
- closes: CLI-2269
@supabase-cli-releaser
chore: sync API types from infrastructure (#6402)
1ff3fd6 
This PR was automatically created to sync API types from the
infrastructure repository.

Changes were detected in the generated API code after syncing with the
latest spec from infrastructure.

Co-authored-by: supabase-cli-releaser[bot] <246109035+supabase-cli-releaser[bot]@users.noreply.github.com>
@avallete @cursoragent
feat(cli): add SUPABASE_USE_SLIM_IMAGES flag for slim ghcr images (#6382
de133cf 
)

## Summary

Adds an opt-in ambient env flag `SUPABASE_USE_SLIM_IMAGES` (`true` or
`1`) that rewrites local-stack Docker image names from the embedded
Dockerfile pins to the slim `ghcr.io/supabase/cli/` builds.

Published slim postgres/storage/auth/edge-runtime images now match the
docker.io contracts (root start, `sh`/`wget`), so the flag is an
image-name rewrite rather than a second runtime. Spec builders still
branch for services that remain distroless (auth/studio/pg-meta
healthchecks, pooler/realtime/analytics busybox wget, Vector
`secretFiles`). Kong, the `differ`/`migra`/`pgprove` job images, PG14,
OrioleDB, historical 15.x pins, and `deno_version = 1` stay on
docker.io. Slim refs skip `SUPABASE_INTERNAL_IMAGE_REGISTRY`. With the
flag unset, image *names* stay on docker.io.

This PR also bumps the shared Dockerfile pins (flag-off and flag-on use
the same versions) and syncs stack `DEFAULT_VERSIONS`:

- postgres `17.6.1.165` → `17.6.1.167`
- postgres 15 fallback `15.8.1.085` → `15.14.1.167` (slim-services
[#290](supabase/slim-services#290); published as
`ghcr.io/supabase/cli/postgres:15.14.1.167`)
- pooler `2.9.7` → `2.9.12`
- realtime `v2.129.9` → `v2.130.0`
- storage `v1.71.0` → `v1.72.1`

Majors 13/15 slim-translate that current PG15 pin when the flag is on.
Storage `v1.72.1` prefers `IMAGE_TRANSFORMATION_ENABLED` over
`ENABLE_IMAGE_TRANSFORMATION`, so the CLI now emits both keys on every
Storage spec (not slim-only).

The rewrite always targets `ghcr.io/supabase/cli/`. The stack catalog's
vector/pooler mirrors (`ghcr.io/supabase/{vector,supavisor}`) are not
used.

This is the code layer of a stack that splits the previous mixed review
on #6329. Docs live in #6383.

## Linked issue

Closes #

- [x] The linked issue is **open** and carries the
`open-for-contribution` label (or I'm a Supabase maintainer).

## Checklist

- [x] The PR title follows [Conventional
Commits](https://www.conventionalcommits.org/) (e.g. `fix(cli): …`).
- [x] Tests added or updated for the change.
- [ ] From the repository root, `pnpm check:all` passes; relevant
package tests pass for every touched workspace, and `pnpm types:check`
passes for each touched TypeScript workspace (or workspace declaring
it).

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
jgoux and others added 2 commits September 4, 2026 09:48
@jgoux
ci(cli): install release dependencies fresh on Windows (#6464)
7a361f6 
## Summary

The Windows release smoke job fails during dependency setup after
restoring the pnpm global virtual-store cache because `effect-tsgo`
cannot resolve its Windows TypeScript binary. The initial cache-miss run
succeeded, while both cache-hit attempts reproduced the failure.

Skip only the pnpm store cache on Windows in the shared setup action so
fresh installs reconstruct the package links. Keep Go caching on Windows
and preserve all dependency caching on other platforms.
@Coly010
fix(config): correct ProjectConfig's hosted-field coverage (CLI-2316) (…
ca62446 
…#6451)

## Summary

`ProjectConfig` is meant to describe "what a Supabase project looks like
on the platform." This PR corrects its coverage in both directions,
verified against the actual `config-sync` push code and the
OpenAPI-generated API contracts
(`packages/api/src/generated/contracts.ts`) rather than assumption:

**Removes CLI-only fields that leaked in** (`fromConfigDocument`'s
`DOCUMENT_ONLY_LOCAL_PATHS`): local dev ports (`api.port`, `db.port`,
`db.shadow_port`), `api.tls`/`api.external_url`, `db.health_timeout`,
`db.pooler.{enabled,port}`, `db.migrations`, `db.seed`, all of
`realtime.*`, and most of `experimental.*` (OrioleDB/S3 storage-engine
config, `pgdelta`, `inspect`) — none has any live hosted counterpart
under any CLI command. `db.major_version` and
`db.pooler.{pool_mode,default_pool_size,max_client_conn}` were initially
excluded too but restored after review: they're real fields
`v2GetProjectConfig` genuinely reports, and `ProjectConfig` is consumed
by `config diff`/`config pull` today (not `config push`, which still
runs on legacy v1 endpoints) — excluding them made them permanently
unclassifiable, silently blocking `config pull` from ever syncing them.

**Adds genuinely missing hosted fields** (follow-up audit against a
broader field list): `auth.external.figma` (the schema had no `figma`
provider at all, despite a real `external_figma_*` API surface — already
flagged as a known gap in the registry's own comments),
`auth.sms.otp_length`/`auth.sms.otp_expiry` (new fields for pre-existing
real GoTrue settings neither the legacy shell nor Go's own CLI ever
modeled), and `auth.sms.twilio.content_sid` (same story, Twilio-only).

Everything else audited was either already working correctly (just
needed a gating field like `enabled`/`smtp.enabled` set to observe it)
or is deliberately not hosted, confirmed per-item against the real API:
`skip_nonce_check` has no API field for any provider except google;
plain `slack` (vs. `slack_oidc`) is an existing Go-parity deprecation
this schema intentionally never modeled;
`experimental.s3_host`/`s3_region`/the S3 credential pair have no API
counterpart anywhere. `auth.oauth_server.*` is correctly mapped on the
API arm but unconditionally dropped from the document arm by the
pre-existing `applyPushUnmanagedOmissions` — that's explicitly Linear
CLI-2314's planned scope (retire push-capability pruning), not addressed
here.

Added a standing integrity test asserting no registry-mapped field can
ever land in the CLI-only exclusion list, which would have caught the
`db.major_version`/`db.pooler` regression automatically. ADR 0021/0022
updated to record the corrected family and the invariant.

Linear: CLI-2316
depthfirst-app[bot]
depthfirst-app Bot reviewed Sep 4, 2026
View reviewed changes
Comment thread .github/workflows/release-config.yml
@@ -0,0 +1,515 @@
name: Release Config

@depthfirst-app depthfirst-app Bot Sep 4, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Severity: MEDIUM

The existing ownerless /.github/workflows/*.yml CODEOWNERS rule still covers this newly added production release workflow. An unreviewed workflow change could alter the App-token, OIDC, artifact, or npm-publish steps and publish attacker-controlled package contents without required CLI-owner review.
Helpful? Add 👍 / 👎

💡 Fix Suggestion

Suggestion: Add an explicit @supabase/cli ownership entry for release-config.yml in .github/CODEOWNERS, placing it alongside the other sensitive workflow overrides (after line 22, where github-scripts-ci.yml is declared). The ownerless /.github/workflows/*.yml rule (line 6) currently takes precedence via last-match-wins semantics only for patterns listed later — but since lines 21-22 demonstrate the pattern for reasserting ownership, add the following line in that same block:

/.github/workflows/release-config.yml @supabase/cli

This mirrors what was done for ai-review.yml and github-scripts-ci.yml and ensures that any PR modifying the production release workflow — which mints GitHub App tokens and publishes npm packages — requires mandatory review from a CLI maintainer before merging.

Comment thread .github/workflows/mirror-slim-image.yml
@@ -0,0 +1,203 @@
name: Mirror Slim Image

@depthfirst-app depthfirst-app Bot Sep 4, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Severity: MEDIUM

This newly added workflow remains covered by the ownerless /.github/workflows/*.yml CODEOWNERS rule despite assuming a production AWS role with id-token: write and copying images into public ECR. An unreviewed workflow modification could bypass digest checks or redirect the mirror, poisoning published runtime images.
Helpful? Add 👍 / 👎

💡 Fix Suggestion

Suggestion: Add an explicit CODEOWNERS ownership override for mirror-slim-image.yml in .github/CODEOWNERS, appended after the existing sensitive-workflow overrides block. Specifically, add the line /.github/workflows/mirror-slim-image.yml @supabase/cli after the /.github/workflows/github-scripts-ci.yml @supabase/cli entry. Because the /.github/workflows/*.yml pattern is intentionally left ownerless to allow Dependabot auto-merges, this new workflow — which assumes a production AWS role (PROD_AWS_ROLE) with id-token: write and publishes to public ECR — falls through to that ownerless rule. The 'last matching pattern wins' CODEOWNERS semantics mean an explicit override at the bottom of the file will restore mandatory maintainer review for this workflow, preventing unauthorized modifications from bypassing digest checks or redirecting the ECR mirror.

Prashansa-K and others added 4 commits September 4, 2026 11:14
@Prashansa-K
chore: removed the next folder from the cli directory (#6465)
0489a3d 
## Summary

next version of the CLI is a scraped project at the moment. Thus,
removing these files so as to reduce confusion.
If required in future, we can always access these via git history.

#### Brief of changes
- Restored genuinely-shared infrastructure from `next/` into
`src/shared/` (auth, config, cli/command-docs) with corrected import
paths, since legacy actually depends on it.
- Fixed all downstream breakage: import paths across shared/cli/run.ts,
telemetry layers, test helpers (mocks.ts), and scripts/generate-docs.ts.
- Modified release tooling to drop the next/alpha shell entirely.
- Removed unused dependencies.
- Rewrote a few things so that references of `next` could be removed
from tests, test-helpers or docs.

#### Deliberately left untouched
`apps/cli/AGENTS.md` and `apps/cli/CLAUDE.md` — describes the stale
two-shell architecture
`apps/cli/docs/platform-command-generation.md` — documents supabase api
routes/api request, a feature that only ever existed in `next/`.
`apps/cli/docs/go-cli-divergences.md`
The above documents can be changed later once we shift the legacy CLI
directly under `src`.

## Checklist

- [x] The PR title follows [Conventional
Commits](https://www.conventionalcommits.org/) (e.g. `fix(cli): …`).
- [x] Tests added or updated for the change - NA.
- [x] From the repository root, `pnpm check:all` passes; relevant
package tests pass for every touched workspace, and `pnpm types:check`
passes for each touched TypeScript workspace (or workspace declaring
it).
@Coly010
feat(cli): rebuild config push as diff-first partial updates (CLI-231…
cb8041a 
…3) (#6454)

## Summary

`supabase config push` is rebuilt as a **diff-first** command. It reads
the project's effective
configuration once (`GET /v2/projects/{ref}/config`), runs the same
`diffProjectConfig` that
`config diff` and `config pull` use, and writes only the properties your
`supabase/config.toml`
declares *and* that differ from the project — as sparse request bodies
to the six existing v1 update
endpoints.

The previous pipeline (six per-service v1 GETs → rebuild each service's
full local subset with
hand-coded presence/enabled gates → TOML unified diff → PUT/PATCH the
whole subset) is deleted:
`push/config-sync/**`, the TOML encoder and diff renderer, and
`push.raw-presence.ts`.

Linear: CLI-2313. The optional follow-up to swap the six v1 writes for
the single v2 PATCH once that
endpoint ships is CLI-2317; the `@supabase/config` cleanup this unblocks
is CLI-2314 (no
`packages/config` changes here).

## What changed

- `push.plan.ts` — routes every comparable `ProjectConfig` path to one
of six write resources
(`api`, `db.settings`, `db.network_restrictions`, `db.ssl_enforcement`,
`auth`, `storage`) or to an
explicit *unsupported* set (`db.major_version`, `db.pooler.*`,
`auth.oauth_server.*`); owns the
resource gates, the MFA add-on gates and the resource→response-block
mapping. A unit test asserts
every registry path is classified, so a new `@supabase/config` row
cannot fall through silently.
- `push.encoders.ts` — six pure encoders turning routed changes into
sparse bodies. Groups the API
requires together still ship whole (CIDR lists, storage feature blocks,
SMTP, captcha, each auth
hook, each OAuth provider, the active SMS provider); **undeclared
members of such a group are sent
with the project's current value read in the same run**, so they do not
change. Only when the API
did not return a member's value is the config default sent, and that is
disclosed in the
confirmation block as `[group-write]`. The storage encoder can emit `{
enabled: false, … }` for
`icebergCatalog`/`vectorBuckets`, which the old builder structurally
could not.
- `push.secrets.ts` — declared secrets are compared as HMAC digests
against what the API reports;
plaintext is sent only when the digest differs or the remote has no
value. Empty values and
unresolved `env(...)` references are never sent and are now disclosed
before the prompt.
- `push.format.ts` — per-service change blocks reuse the family's
per-property renderer
(`config/config.format.ts`), plus the new notes, the machine-readable
summary message and the JSON
  payload.
- `push.handler.ts` — one read, then per-resource encode → confirm →
write in the established order. A
resource whose block the API did not return is reported `unavailable`
and never written; a response
  with no configuration blocks at all is an error (nothing is written).
- Family-root hoists shared by `config diff`, `config pull` and `config
push`:
  `config/config.read-status.ts` (401/403/404 read-status messages) and
`config/config.project-config.ts` (the `ProjectConfigParseError` guard).
Both handlers now use them
  instead of private copies.
- Test infrastructure: `mockLegacyPlatformApiService` gains `executeRaw`
support; the v2 response
fixture is shared between the `config diff` and `config push` suites;
the cli-e2e replay scenarios
  and recorded fixtures reflect the new request sequence.
- `SIDE_EFFECTS.md` rewritten for the new routes, output, statuses and
exit causes.

## Behavior changes (user-visible)

1. **One read instead of six.** `GET /v2/projects/{ref}/config` replaces
the six per-service
`GET /v1/…` calls. `GET /v1/projects/{ref}/billing/addons` is unchanged.
2. **Undeclared properties are left alone.** Previously a property
absent from `config.toml` was
written back with its schema default whenever its service was pushed.
Now only declared, differing
properties are written; members of a required-together group keep their
current project value.
`config diff` shows the remaining drift, and the push output reports how
many remote properties
   were left untouched.
3. **Requests carry only what changed** (plus the required-together
groups above).
4. **Credentials are compared before being sent**; unchanged secrets are
not re-sent, and a credential
that cannot be sent (empty / unresolved `env(...)`) is shown in the
confirmation block.
5. **Per-service change display** is now the same per-property format
`config diff` prints
(`path [update]`, `local:` / `remote:`) instead of a TOML-style unified
diff. Secret values are
   never printed.
6. **New reporting**: a `Comparison scope:` line on every run; notes for
properties with no Management
API field, properties that could not be encoded as written (with the
reason), declared properties
the command does not manage (count), remote-only drift (count), and
group members written at a
   default.
7. **Partial API responses are never written blind.** A resource whose
configuration block was not
returned is reported `unavailable` and skipped; if no blocks are
returned the command exits 1.
8. **JSON / stream-json payload** gains `schema_version: 1`,
`services[].changes`, `unsupported`,
`unencodable`, `forced`, `unmanaged`, `secrets`
(`sent`/`unchanged`/`not_set`/`gated`/`skipped`,
reflecting the write that actually happened), `declined_addons`,
`remote_only`, `scope`, and a
non-empty summary `message`. Existing fields (`project_ref`,
`services[].service`,
`services[].status`) keep their values; `status` gains `unavailable` and
`not_pushable`.
9. **Declining an MFA cost prompt** behaves as before (both
`verify_enabled` and `enroll_enabled` are
sent as `false` when the project has either enabled) and is now recorded
in `declined_addons`.
10. **Command description** now states the hands-off rule and points at
`config diff` as the preview.
11. **Unchanged**: command path and flags, prompt wording, `Pushing
config to project:` /
`Remote <service> config is up to date.` / `Updating <service> service
with config:` /
`Enabling webhooks for project:` lines, exit codes (declining a prompt
still exits 0), files read
    and written, telemetry.

## Reviewer notes

- Storage feature *disable* is encoder-ready but not yet reachable:
`@supabase/config` still prunes a
disabled `storage.analytics`/`storage.vector` from the local projection
(`applyPushUnmanagedOmissions`), so such a change surfaces in the
`unmanaged` count today and starts
  being pushed when CLI-2314 lands.
- The one `Effect.die` arm in `legacyConfigProjectConfigTry` is
unreachable from a JSON-parsed body
(every `@supabase/config` failure is a `ProjectConfigParseError`) and is
covered by its unit test
  rather than the integration suites.
@7ttp
test(cli): harden live e2e assertions (CLI-2315) (#6466)
0f41026 
## TL;DR
hardens seven live e2e tests so a real regression fails and a platform
read after write doesn't race
and gives `gen types` the registry fallback every other container
command already has so the suite's recurring ECR rate-limit failure goes
away...

## whats introduced?
- `postgres-config update`: proves the override through `get` by polling
until the platform reports it, instead of a single read that raced the
write
- `postgres-config delete`: the same poll for the seed proof and the
absence proof
- `db dump`: asserts the dump file contains schema DDL instead of only
existing
- `migration list`: asserts the migrations table header renders instead
of only "not Unauthorized"
- `orgs list`: asserts the table header and at least one organization
row
- `functions list`: asserts the functions table header renders instead
of only "not Unauthorized"
- `link`: asserts the cached ref in `linked-project.json` is the linked
project instead of only checking the file exists
- `tests/helpers/live.ts`: `expectPostgresConfigLiveOverride`, a bounded
`expect.poll` over `postgres-config get -o json` whose failure carries
the label, stdout and stderr
- extra, `gen types`: resolves the pg-meta image through the shared
resolver before running it, cached copy first, then ECR, GHCR and Docker
Hub with retries, instead of one `docker run` against a single registry;
the resolve sits outside the pooler fallback so a pull failure is never
mistaken for an IPv6 error

## ref:
- closes: CLI-2315
- extends: #6427
@Coly010
fix(config): retire push-capability pruning from ProjectConfig (CLI-2…
2677ccc 
…314) (#6469)

## Summary

`fromConfigDocument` baked the legacy `config push` pipeline's
write-capability envelope into the
shared `ProjectConfig` representation (ADR 0021's original "push
convergence" ruling). That was
right when the CLI's own push command was the only reader; it's wrong
now that Studio reads the
same package for drift detection via the Management API, an actor with
none of push's write-path
limitations. Concretely, this hid real hosted customization from every
consumer — not just push —
behind three families of unconditional/blanket omissions.

Builds on #6454 (CLI-2313, merged into `develop`) — this branch has
already been rebased onto
`develop` post-merge. Nothing here depends on the v2 PATCH endpoint
(BRA-245/CLI-2317); everything
works over the v1 write endpoints #6454 already wired up.

Linear: [CLI-2314](https://linear.app/supabase/issue/CLI-2314).

## What changed

- **`applyPushUnmanagedOmissions` deleted** — this unconditionally
dropped the whole
`auth.oauth_server` subtree and dropped
`storage.analytics`/`storage.vector` entirely whenever
`enabled: false`, because legacy push never sent those shapes. That
pipeline no longer exists
(CLI-2313 deleted `config-sync/*.sync.ts`); push now consumes
`ProjectConfig` directly.
- **`DISABLED_SENTINEL_PRUNES` re-derived from the platform's actual
data model**, not from what
legacy push happened to send. Every surviving entry's docstring now
states a real, verified
reason a sibling field goes inert server-side when its container is off
(e.g. `api.enabled` is
the same wire fact as `db_schema.length > 0`, not an independent field
the API arm doesn't
already gate on its own). A new cross-arm symmetry test makes this
machine-checked: a disabled
document projection and the equivalent disabled API-response projection
must be byte-identical.
- **Deleted the `auth.enabled`/`storage.enabled` blanket
section-prunes.** These had nothing to do
with the platform — `auth.enabled` is literally "Enable the local GoTrue
service" with no
hosted/registry equivalent, yet disabling it wiped the *entire* rest of
the `auth` section (SMTP,
external providers, captcha, everything) from the shared representation
for anyone reading it.
Fixed a real bug this exposed: `push.plan.ts`'s
`legacyPushResourceEnabled` was gating the
*entire* `auth`/`storage` resource dispatch on that same local toggle,
so a declared change could
be silently dropped. `auth`/`storage` now follow the same no-gate
pattern `api`/`db.settings`
already used. No new "default comparison" machinery was needed —
`diffProjectConfig`'s existing
`declared` flag (computed generically from raw TOML presence for every
comparable path) already
keeps an undeclared default value from ever being pushed over a real
hosted customization.
- **`auth.oauth_server.*` wired up as genuinely pushable.** It's
writable via `UpdateAuthConfigBody`
(confirmed against the OpenAPI spec) — push's own `SIDE_EFFECTS.md` had
been carrying it in the
unsupported-prefix list as an explicitly-labeled placeholder for this
exact issue.
- **Named `ConfigAbsencePolicy`** (`"absent-is-default"` /
`"absent-is-hands-off"`) for the two
operand policies `fromConfigDocument` always implicitly implemented
depending on which overload
you called. Documents the one genuinely hazardous cell (an absent field
masquerading as a real
declaration when diffing in dense mode) and the `declaredRoot = {}`
cliff a caller hits by
  omitting `document` — exactly the calling shape Studio would use.
- **Unmanaged caveat reworded** to actor-neutral language ("not managed
while its section is
  disabled" instead of "cannot be pushed").
- **ADR 0021 addendum** reframing `ProjectConfig` as a shared
multi-actor representation, plus
matching touch-ups to ADR 0022/0023 and cleanup of stale references to
the deleted function.

## Verification (post-rebase onto `develop`)

- `packages/config`: `bun --bun vitest run --project unit` — 1264
passed.
- `apps/cli`: `pnpm types:check` clean; `pnpm test:unit` — 5984 passed,
1 skipped;
  `pnpm test:integration` — 3438 passed.

## Follow-ups (out of scope here)

- Consider a `local.auth.enabled`/`local.storage.enabled` namespace so
`supabase start`'s "run this
Docker service" concept is structurally separate from hosted management,
instead of overloading
  `auth.enabled`/`storage.enabled`.
- Audit `LEGACY_PUSH_UNSUPPORTED_PREFIXES`'s remaining `db.pooler` entry
against the OpenAPI spec —
`pool_mode`/`default_pool_size` are writable via
`UpdateSupavisorConfigBody`, only
  `max_client_conn` genuinely isn't.
jgoux and others added 5 commits September 4, 2026 20:02
@jgoux
chore: upgrade Bun to 1.4.1 (#6470)
d35e892 
## Summary

- pin Bun 1.4.1 through mise and refresh the locked runtime artifacts
- replace the Istanbul Vitest coverage provider with the V8 provider
across coverage-enabled workspaces
- remove the unused coverage provider from the CLI e2e workspace and
preserve pnpm global-store peer resolution

[Bun
1.4.1](https://bun.com/blog/bun-v1.4.1#node-js-compatibility-improvements)
fixes the Vitest/c8 V8 coverage merge failure that previously blocked
this migration.

## Binary size impact

Compared locally built Bun 1.4.1 executables with the checksum-verified
[v2.117.0-beta.18 production
artifacts](https://github.com/supabase/cli/releases/tag/v2.117.0-beta.18),
which embed Bun 1.4.0.

| Platform | Production 1.4.0 | Local 1.4.1 | Change |
|---|---:|---:|---:|
| macOS arm64 | 69.52 MiB | 67.53 MiB | -2.86% |
| macOS x64 | 76.00 MiB | 74.20 MiB | -2.37% |
| Linux arm64 | 91.92 MiB | 90.36 MiB | -1.70% |
| Linux x64 | 92.58 MiB | 91.01 MiB | -1.69% |
| Windows arm64 | 84.50 MiB | 83.17 MiB | -1.57% |
| Windows x64 | 94.52 MiB | 91.54 MiB | -3.16% |

The compressed release archives are also 0.37%-1.54% smaller.

The comparison is not fully runtime-isolated: the current source is one
commit beyond the production tag, and the local macOS binaries lack CI
release signing. Linux and Windows provide the cleanest indication of
the Bun upgrade size impact.
@7ttp
fix(cli): read stdin on demand (CLI-2223) (#6450)
c7e6481 
## TL;DR

 follow-up to #6290 Piped answers past the 1024th line were dropped. 
stdin is now read one chunk at a time as prompts ask for it, so nothing
is dropped and the rest stays in the pipe...

## what was biting?

Bun reads a pipe as fast as it fills and cannot be paused, so #6290
drained it into a queue of 1024 lines to stop
 `yes | supabase db push` from eating memory. 
Anything past 1024 lines fell off the queue and those prompts took their
default...

## why this approach is better? 

A file stream over fd 0 honours backpressure, so there is no queue and
no cap.
Memory is bounded the same way Go's `bufio.Scanner` did it: a line over
64 KiB ends line reading and every prompt from then on takes its
default...

## ref:
- adds onto issue: #6287
- extends: #6290
@7ttp
test(cli): narrow config pull live pin (CLI-2324) (#6468)
adc1dfa 
## TL;DR 

spotted in:
https://github.com/supabase/cli/actions/runs/33807759564/job/100822219503
passes now: https://github.com/supabase/cli/actions/runs/33867343063

## ref:
- closes: CLI-2324
- same as: #6437
@kanadgupta @claude
ci(cli): cache only the pnpm content store, not the virtual store (#6471
d6a376c 
)

## Summary

Since #6424 enabled `virtualStoreType: global`, `pnpm store path`
includes `links/`, the global virtual store. It is a tree of directory
links between packages: symlinks on POSIX, NTFS junctions on Windows.
The shared setup action cached that whole directory, and on Windows the
junctions do not survive the actions/cache tar round trip as traversable
directories. pnpm then trusts every restored `links/` directory as
complete and skips relinking, so the first dependency resolved through a
restored junction fails. That is the `DiscoveryError: Unable to resolve
@typescript/typescript-win32-x64` from the root `prepare` script in
[this release
run](https://github.com/supabase/cli/actions/runs/33854068778/job/100967241418).

The failure was deterministic, not transient: every Windows release
smoke-test with a pnpm-store cache hit failed, and the only success with
the new store layout was the cache-miss run that populated the cache.
The earlier Windows failures that week were the unrelated CRLF
patch-file problem fixed in #6461.

## Changes

- Cache only `files/` and the SQLite index of the pnpm store, never
`links/`. pnpm rebuilds the virtual store from the cached files with
hardlinks and no network. The first Linux jobs after #6424 already
demonstrated this path when they restored an older files-only archive
via `restore-keys`.
- Bump the cache key prefix to `pnpm-store-files-…`. actions/cache
restores whatever an archive contains regardless of the current `path`
input, so without the bump Windows would keep restoring the existing
archive that carries `links/` until the lockfile changed.
- Remove the Windows-only cache exclusion from #6464, restoring
dependency caching on the Windows release jobs.

## Reviewer context

The release workflow only runs on `develop`, so PR CI exercises the new
caching on Linux but not the Windows smoke-test job. The first run on
each OS will be a cache miss under the new prefix. The second Windows
release run after merge is the real confirmation, since it is the first
cache hit.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
@johnstonmatt
feat(workers): add exposure control and new --instances flag (#6432)
2c66579 
Adds an `exposure` dial (`public`/`private`) for worker deployments
alongside the existing runtime/size/instances dials, and lets `workers
new` set instance count up front instead of only through `push`.

- Add `exposure` as a closed set (`public`/`private`) on `workers new`
and `workers push`, recorded in `config.toml`/`config.json` and resolved
with the same precedence as size/runtime: flag override, then recorded
value, then `public` default; an unrecognized recorded value refuses the
deploy rather than silently coercing it.
- Add `--instances` to `workers new`, written to `config.toml` only when
it differs from the default of 1, and rendered as a bare TOML number
rather than a quoted string.
- Extend `toml-section.ts` and `worker-config.ts` to support writing
numeric values, and update the config schema/docs
(`packages/config/src/workers.ts`, `config.schema.json`,
`project-config.schema.json`) to describe `exposure`.
- Add `UnknownWorkerExposureError` and corresponding unit/integration
test coverage across both commands.
avallete and others added 5 commits September 7, 2026 07:37
@avallete @claude
fix(cli): honour deletion of extension-managed objects in declarative…
25ffc73 
… sync (#6449)

Removing a `pg_cron` job or `pgmq` queue declaration from a
manifest-less declarative tree was refused as a legacy pg-delta export,
and the refusal then blocked every later sync of that tree, unrelated
schema work included. The engine already plans the `cron.unschedule` /
`pgmq.drop_queue` calls; the refusal was CLI-side classification.

The legacy-export gate now only fires when the plan drops an extension.
Extension-managed object removals (cron jobs, pgmq queues) no longer
count toward it, so deleting or renaming one on a converged tree
generates the unschedule / drop_queue statements like any other change.
The gate still enumerates those objects as evidence when their owning
extension itself is being dropped, which is the legacy-export case it
was built for.

No new flags, prompts, or warning output. The change is confined to
`legacyClassifyDeclarativeCompatibilityGap` in `declarative.flow.ts`,
plus an integration scenario and an e2e scenario that adds a job and a
queue to the tree, then renames the job and drops the queue.

Resolves CLI-2282.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01Wh8sCVwt29sYWSYdcDUbWN

---------

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
@Prashansa-K
chore: restructured cli directory - flatten src/legacy/* into src/ (#…
5ba4bc8 
…6486)

## Summary

PR changes:
-
src/legacy/{auth,cli,commands,config,docs,output,telemetry,main.ts,SIDE_EFFECTS_TEMPLATE.md}
moved up to src/*
- src/legacy/shared/* moved and renamed to src/command-internal/*
- top-level src/shared/ (pre-existing, cross-cutting infra) is untouched
by this move

This change is in conjunction to #6465. 
Since `next` CLI project is on hold at the moment, we are restructuring
the directory
so as to make it easy for new contributors and avoid any confusion.

## Checklist

- [x] The PR title follows [Conventional
Commits](https://www.conventionalcommits.org/) (e.g. `fix(cli): …`).
- [x] Tests added or updated for the change - NA
- [x] From the repository root, `pnpm check:all` passes; relevant
package tests pass for every touched workspace, and `pnpm types:check`
passes for each touched TypeScript workspace (or workspace declaring
it).
@dependabot
chore(ci): bump the actions-major group across 1 directory with 6 upd…
3cda58e 
…ates (#6484)

Bumps the actions-major group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [openai/codex-action](https://github.com/openai/codex-action) | `1.11`
| `1.12` |
| [github/codeql-action/init](https://github.com/github/codeql-action) |
`4.37.7` | `4.37.9` |
|
[github/codeql-action/analyze](https://github.com/github/codeql-action)
| `4.37.7` | `4.37.9` |
|
[aws-actions/configure-aws-credentials](https://github.com/aws-actions/configure-aws-credentials)
| `6.2.3` | `6.2.4` |
|
[softprops/action-gh-release](https://github.com/softprops/action-gh-release)
| `3.0.2` | `3.0.3` |
|
[linear/linear-release-action](https://github.com/linear/linear-release-action)
| `0.15.1` | `0.17.1` |


Updates `openai/codex-action` from 1.11 to 1.12
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/openai/codex-action/blob/main/CHANGELOG.md">openai/codex-action's
changelog</a>.</em></p>
<blockquote>
<h1>codex-action Changelog</h1>
<h2><a
href="https://github.com/openai/codex-action/tree/v1.12">v1.12</a>
(2026-08-20)</h2>
<ul>
<li>Strengthen Linux runner privilege isolation and Responses API proxy
credential handling.</li>
<li>Reject Codex arguments and configuration overrides that conflict
with protected execution settings.</li>
<li>Require unprivileged user namespaces for Linux
<code>drop-sudo</code>; run the action after steps that need
<code>sudo</code>, Docker, or privileged service sockets.</li>
<li>Document runner requirements, permission-profile behavior, and
trusted configuration boundaries.</li>
</ul>
<h2><a
href="https://github.com/openai/codex-action/tree/v1.11">v1.11</a>
(2026-07-04)</h2>
<ul>
<li><a
href="https://redirect.github.com/openai/codex-action/pull/116">#116</a>
keep the permission profile helper backward compatible</li>
</ul>
<h2><a
href="https://github.com/openai/codex-action/tree/v1.10">v1.10</a>
(2026-07-02)</h2>
<ul>
<li><a
href="https://redirect.github.com/openai/codex-action/pull/113">#113</a>
add Codex permission profile support</li>
</ul>
<h2><a href="https://github.com/openai/codex-action/tree/v1.9">v1.9</a>
(2026-06-22)</h2>
<ul>
<li><a
href="https://redirect.github.com/openai/codex-action/pull/85">#85</a>
update the internal <code>setup-node</code> pin to
<code>v6.3.0</code></li>
</ul>
<h2><a href="https://github.com/openai/codex-action/tree/v1.8">v1.8</a>
(2026-04-29)</h2>
<ul>
<li><a
href="https://redirect.github.com/openai/codex-action/pull/91">#91</a>
tighten what bots are allowed</li>
</ul>
<h2><a href="https://github.com/openai/codex-action/tree/v1.7">v1.7</a>
(2026-04-24)</h2>
<ul>
<li><a
href="https://redirect.github.com/openai/codex-action/pull/89">#89</a>
restrict bot permission bypass</li>
</ul>
<h2><a href="https://github.com/openai/codex-action/tree/v1.6">v1.6</a>
(2026-03-16)</h2>
<ul>
<li><a
href="https://redirect.github.com/openai/codex-action/pull/77">#77</a>
enable GitHub-hosted Linux bubblewrap support</li>
</ul>
<h2><a href="https://github.com/openai/codex-action/tree/v1.5">v1.5</a>
(2026-03-16)</h2>
<ul>
<li><a
href="https://redirect.github.com/openai/codex-action/pull/74">#74</a>
harden shell interpolation in action workflows</li>
</ul>
<h2><a href="https://github.com/openai/codex-action/tree/v1.4">v1.4</a>
(2025-11-19)</h2>
<ul>
<li><a
href="https://redirect.github.com/openai/codex-action/pull/58">#58</a>
revert <a
href="https://redirect.github.com/openai/codex-action/issues/56">#56</a>
and use the latest stable version of Codex CLI again</li>
</ul>
<h2><a href="https://github.com/openai/codex-action/tree/v1.3">v1.3</a>
(2025-11-19)</h2>
<ul>
<li><a
href="https://redirect.github.com/openai/codex-action/pull/56">#56</a>
temporarily set the default version of Codex CLI to
<code>0.58.0</code></li>
</ul>
<h2><a href="https://github.com/openai/codex-action/tree/v1.2">v1.2</a>
(2025-11-07)</h2>
<ul>
<li><a
href="https://redirect.github.com/openai/codex-action/pull/52">#52</a>
add <code>baseUrl</code> to <code>Octokit</code> constructor, if
appropriate, for GHE</li>
</ul>
<h2><a href="https://github.com/openai/codex-action/tree/v1.1">v1.1</a>
(2025-11-05)</h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/openai/codex-action/commit/86365089eb2b84e0a8fb0717b304f8bdcb13b20e"><code>8636508</code></a>
fix: improve runner setup and configuration handling</li>
<li><a
href="https://github.com/openai/codex-action/commit/c385816875cc2fc8e033ed9d1cba96f8c331210e"><code>c385816</code></a>
Retry network errors/transient HTTP errors in GitHub API requests (<a
href="https://redirect.github.com/openai/codex-action/issues/128">#128</a>)</li>
<li><a
href="https://github.com/openai/codex-action/commit/dd78cb653811af44014baa08fe954e28d32c1bf9"><code>dd78cb6</code></a>
docs: update CHANGELOG for v1.11 (<a
href="https://redirect.github.com/openai/codex-action/issues/117">#117</a>)</li>
<li>See full diff in <a
href="https://github.com/openai/codex-action/compare/52fe01ec70a42f454c9d2ebd47598f9fd6893d56...86365089eb2b84e0a8fb0717b304f8bdcb13b20e">compare
view</a></li>
</ul>
</details>
<br />

Updates `github/codeql-action/init` from 4.37.7 to 4.37.9
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/github/codeql-action/releases">github/codeql-action/init's
releases</a>.</em></p>
<blockquote>
<h2>v4.37.9</h2>
<ul>
<li>Update default CodeQL bundle version to <a
href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.4">2.26.4</a>.
<a
href="https://redirect.github.com/github/codeql-action/pull/4106">#4106</a></li>
</ul>
<h2>v4.37.8</h2>
<p>No user facing changes.</p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/github/codeql-action/blob/main/CHANGELOG.md">github/codeql-action/init's
changelog</a>.</em></p>
<blockquote>
<h1>CodeQL Action Changelog</h1>
<p>See the <a
href="https://github.com/github/codeql-action/releases">releases
page</a> for the relevant changes to the CodeQL CLI and language
packs.</p>
<h2>[UNRELEASED]</h2>
<ul>
<li>The CodeQL Action now supports CodeQL releases that are compatible
with Linux Arm64 and downloads the native <code>linux-arm64</code>
CodeQL bundle when available. <a
href="https://redirect.github.com/github/codeql-action/pull/4072">#4072</a></li>
</ul>
<h2>4.37.9 - 26 Aug 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a
href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.4">2.26.4</a>.
<a
href="https://redirect.github.com/github/codeql-action/pull/4106">#4106</a></li>
</ul>
<h2>4.37.8 - 21 Aug 2026</h2>
<p>No user facing changes.</p>
<h2>4.37.7 - 13 Aug 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a
href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.3">2.26.3</a>.
<a
href="https://redirect.github.com/github/codeql-action/pull/4085">#4085</a></li>
</ul>
<h2>4.37.6 - 04 Aug 2026</h2>
<ul>
<li>Changed the default filepath for the new remote file address format
that was introduced in CodeQL Action 4.37.0 / 3.37.0 to
<code>.github/codeql-config.yml</code> to align it with the suggested
path that is used elsewhere. <a
href="https://redirect.github.com/github/codeql-action/pull/4070">#4070</a></li>
</ul>
<h2>4.37.5 - 03 Aug 2026</h2>
<ul>
<li>Fixed a bug where a network error while streaming the download of
the CodeQL bundle could terminate the <code>init</code> Action instead
of falling back to downloading the bundle before extracting it. <a
href="https://redirect.github.com/github/codeql-action/pull/4061">#4061</a></li>
</ul>
<h2>4.37.4 - 29 Jul 2026</h2>
<ul>
<li>This version of the CodeQL Action adds support for the
<code>tools</code> input for the <code>codeql-action/init</code> step to
be specified using a <code>github-codeql-tools</code> <a
href="https://docs.github.com/en/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization">repository
property</a>. This feature will gradually be rolled out following the
release of this version. Once rolled out, this allows for the CodeQL CLI
version that is used in GitHub-managed workflows, such as Default Setup,
to be set to a custom value. For example, customers who run into issues
with rate limits when a new CodeQL CLI version is released can set the
value to <code>toolcache</code> to always use the CodeQL CLI version
that is available in the runner toolcache. For Advanced Setup workflows,
the value provided for <code>tools</code> in the workflow definition
always takes precedence unless the value of the repository property
starts with <code>!</code>. <a
href="https://redirect.github.com/github/codeql-action/pull/4037">#4037</a></li>
<li>Update default CodeQL bundle version to <a
href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.2">2.26.2</a>.
<a
href="https://redirect.github.com/github/codeql-action/pull/4051">#4051</a></li>
</ul>
<h2>4.37.3 - 22 Jul 2026</h2>
<p>No user facing changes.</p>
<h2>4.37.2 - 21 Jul 2026</h2>
<ul>
<li>The new address format for the <code>config-file</code> input that
was introduced in CodeQL Action 4.37.0 is now enabled by default. In
addition to the format described there, the <code>remote=</code> prefix
can now be used to explicitly indicate that the input refers to a remote
file. All previous input formats continue to be accepted as well. <a
href="https://redirect.github.com/github/codeql-action/pull/4023">#4023</a></li>
<li>The CodeQL Action can now make use of <a
href="https://docs.github.com/en/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries">configured
private registries</a> in Default Setup to retrieve CodeQL configuration
files from remote repositories that require authentication. This will
allow customers to store their CodeQL configuration in a single
repository that can then be referenced by Default Setup workflows in
other repositories. We expect to roll this and other, related changes
out to everyone in July. <a
href="https://redirect.github.com/github/codeql-action/pull/4007">#4007</a></li>
</ul>
<h2>4.37.1 - 16 Jul 2026</h2>
<ul>
<li><em>Upcoming breaking change</em>: Add a deprecation warning for
customers using CodeQL version 2.20.6 and earlier. These versions of
CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise
Server 3.16, and will be unsupported by the next minor release of the
CodeQL Action. <a
href="https://redirect.github.com/github/codeql-action/pull/3956">#3956</a></li>
<li>Update default CodeQL bundle version to <a
href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.1">2.26.1</a>.
<a
href="https://redirect.github.com/github/codeql-action/pull/4019">#4019</a></li>
</ul>
<h2>4.37.0 - 08 Jul 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a
href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.0">2.26.0</a>.
<a
href="https://redirect.github.com/github/codeql-action/pull/3995">#3995</a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/github/codeql-action/commit/cdf488f595d80d6e07e03d4674febd5ab45fa938"><code>cdf488f</code></a>
Merge pull request <a
href="https://redirect.github.com/github/codeql-action/issues/4107">#4107</a>
from github/update-v4.37.9-920ba7cd1</li>
<li><a
href="https://github.com/github/codeql-action/commit/7243f38558d187dde99730d224bb47aa26a95306"><code>7243f38</code></a>
Update changelog for v4.37.9</li>
<li><a
href="https://github.com/github/codeql-action/commit/920ba7cd1596037e042122c00381eb16b397d68e"><code>920ba7c</code></a>
Merge pull request <a
href="https://redirect.github.com/github/codeql-action/issues/4106">#4106</a>
from github/update-bundle/codeql-bundle-v2.26.4</li>
<li><a
href="https://github.com/github/codeql-action/commit/ecfa6e16817b8f490bc9a59baa391baf4fa3e3c2"><code>ecfa6e1</code></a>
Add changelog note</li>
<li><a
href="https://github.com/github/codeql-action/commit/adcdf4a70d247343cf9c29e0f7a6658b51c3a2b1"><code>adcdf4a</code></a>
Update default bundle to codeql-bundle-v2.26.4</li>
<li><a
href="https://github.com/github/codeql-action/commit/486fec2a3ea2626afcd8c7e9208b4f515078dd7e"><code>486fec2</code></a>
Merge pull request <a
href="https://redirect.github.com/github/codeql-action/issues/4099">#4099</a>
from github/update-supported-enterprise-server-versions</li>
<li><a
href="https://github.com/github/codeql-action/commit/134624c67b20869c2aaa36dafa726375b78a5d76"><code>134624c</code></a>
Merge pull request <a
href="https://redirect.github.com/github/codeql-action/issues/4101">#4101</a>
from github/dependabot/npm_and_yarn/npm-minor-457d82...</li>
<li><a
href="https://github.com/github/codeql-action/commit/ff43db8f982a368288f117354fb8d046e937124c"><code>ff43db8</code></a>
Merge pull request <a
href="https://redirect.github.com/github/codeql-action/issues/4103">#4103</a>
from github/mergeback/v4.37.8-to-main-db488dde</li>
<li><a
href="https://github.com/github/codeql-action/commit/4605e03a74cf891614c4d76f82384a16c1c11816"><code>4605e03</code></a>
Rebuild</li>
<li><a
href="https://github.com/github/codeql-action/commit/099c869cad6bf3b88657154d4ae47ffed27e632d"><code>099c869</code></a>
Update changelog and version after v4.37.8</li>
<li>Additional commits viewable in <a
href="https://github.com/github/codeql-action/compare/ff2f1c621b7f889edc0d3c761ac2e6a3f8cdb0dd...cdf488f595d80d6e07e03d4674febd5ab45fa938">compare
view</a></li>
</ul>
</details>
<br />

Updates `github/codeql-action/analyze` from 4.37.7 to 4.37.9
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/github/codeql-action/releases">github/codeql-action/analyze's
releases</a>.</em></p>
<blockquote>
<h2>v4.37.9</h2>
<ul>
<li>Update default CodeQL bundle version to <a
href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.4">2.26.4</a>.
<a
href="https://redirect.github.com/github/codeql-action/pull/4106">#4106</a></li>
</ul>
<h2>v4.37.8</h2>
<p>No user facing changes.</p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/github/codeql-action/blob/main/CHANGELOG.md">github/codeql-action/analyze's
changelog</a>.</em></p>
<blockquote>
<h1>CodeQL Action Changelog</h1>
<p>See the <a
href="https://github.com/github/codeql-action/releases">releases
page</a> for the relevant changes to the CodeQL CLI and language
packs.</p>
<h2>[UNRELEASED]</h2>
<ul>
<li>The CodeQL Action now supports CodeQL releases that are compatible
with Linux Arm64 and downloads the native <code>linux-arm64</code>
CodeQL bundle when available. <a
href="https://redirect.github.com/github/codeql-action/pull/4072">#4072</a></li>
</ul>
<h2>4.37.9 - 26 Aug 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a
href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.4">2.26.4</a>.
<a
href="https://redirect.github.com/github/codeql-action/pull/4106">#4106</a></li>
</ul>
<h2>4.37.8 - 21 Aug 2026</h2>
<p>No user facing changes.</p>
<h2>4.37.7 - 13 Aug 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a
href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.3">2.26.3</a>.
<a
href="https://redirect.github.com/github/codeql-action/pull/4085">#4085</a></li>
</ul>
<h2>4.37.6 - 04 Aug 2026</h2>
<ul>
<li>Changed the default filepath for the new remote file address format
that was introduced in CodeQL Action 4.37.0 / 3.37.0 to
<code>.github/codeql-config.yml</code> to align it with the suggested
path that is used elsewhere. <a
href="https://redirect.github.com/github/codeql-action/pull/4070">#4070</a></li>
</ul>
<h2>4.37.5 - 03 Aug 2026</h2>
<ul>
<li>Fixed a bug where a network error while streaming the download of
the CodeQL bundle could terminate the <code>init</code> Action instead
of falling back to downloading the bundle before extracting it. <a
href="https://redirect.github.com/github/codeql-action/pull/4061">#4061</a></li>
</ul>
<h2>4.37.4 - 29 Jul 2026</h2>
<ul>
<li>This version of the CodeQL Action adds support for the
<code>tools</code> input for the <code>codeql-action/init</code> step to
be specified using a <code>github-codeql-tools</code> <a
href="https://docs.github.com/en/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization">repository
property</a>. This feature will gradually be rolled out following the
release of this version. Once rolled out, this allows for the CodeQL CLI
version that is used in GitHub-managed workflows, such as Default Setup,
to be set to a custom value. For example, customers who run into issues
with rate limits when a new CodeQL CLI version is released can set the
value to <code>toolcache</code> to always use the CodeQL CLI version
that is available in the runner toolcache. For Advanced Setup workflows,
the value provided for <code>tools</code> in the workflow definition
always takes precedence unless the value of the repository property
starts with <code>!</code>. <a
href="https://redirect.github.com/github/codeql-action/pull/4037">#4037</a></li>
<li>Update default CodeQL bundle version to <a
href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.2">2.26.2</a>.
<a
href="https://redirect.github.com/github/codeql-action/pull/4051">#4051</a></li>
</ul>
<h2>4.37.3 - 22 Jul 2026</h2>
<p>No user facing changes.</p>
<h2>4.37.2 - 21 Jul 2026</h2>
<ul>
<li>The new address format for the <code>config-file</code> input that
was introduced in CodeQL Action 4.37.0 is now enabled by default. In
addition to the format described there, the <code>remote=</code> prefix
can now be used to explicitly indicate that the input refers to a remote
file. All previous input formats continue to be accepted as well. <a
href="https://redirect.github.com/github/codeql-action/pull/4023">#4023</a></li>
<li>The CodeQL Action can now make use of <a
href="https://docs.github.com/en/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries">configured
private registries</a> in Default Setup to retrieve CodeQL configuration
files from remote repositories that require authentication. This will
allow customers to store their CodeQL configuration in a single
repository that can then be referenced by Default Setup workflows in
other repositories. We expect to roll this and other, related changes
out to everyone in July. <a
href="https://redirect.github.com/github/codeql-action/pull/4007">#4007</a></li>
</ul>
<h2>4.37.1 - 16 Jul 2026</h2>
<ul>
<li><em>Upcoming breaking change</em>: Add a deprecation warning for
customers using CodeQL version 2.20.6 and earlier. These versions of
CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise
Server 3.16, and will be unsupported by the next minor release of the
CodeQL Action. <a
href="https://redirect.github.com/github/codeql-action/pull/3956">#3956</a></li>
<li>Update default CodeQL bundle version to <a
href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.1">2.26.1</a>.
<a
href="https://redirect.github.com/github/codeql-action/pull/4019">#4019</a></li>
</ul>
<h2>4.37.0 - 08 Jul 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a
href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.26.0">2.26.0</a>.
<a
href="https://redirect.github.com/github/codeql-action/pull/3995">#3995</a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/github/codeql-action/commit/cdf488f595d80d6e07e03d4674febd5ab45fa938"><code>cdf488f</code></a>
Merge pull request <a
href="https://redirect.github.com/github/codeql-action/issues/4107">#4107</a>
from github/update-v4.37.9-920ba7cd1</li>
<li><a
href="https://github.com/github/codeql-action/commit/7243f38558d187dde99730d224bb47aa26a95306"><code>7243f38</code></a>
Update changelog for v4.37.9</li>
<li><a
href="https://github.com/github/codeql-action/commit/920ba7cd1596037e042122c00381eb16b397d68e"><code>920ba7c</code></a>
Merge pull request <a
href="https://redirect.github.com/github/codeql-action/issues/4106">#4106</a>
from github/update-bundle/codeql-bundle-v2.26.4</li>
<li><a
href="https://github.com/github/codeql-action/commit/ecfa6e16817b8f490bc9a59baa391baf4fa3e3c2"><code>ecfa6e1</code></a>
Add changelog note</li>
<li><a
href="https://github.com/github/codeql-action/commit/adcdf4a70d247343cf9c29e0f7a6658b51c3a2b1"><code>adcdf4a</code></a>
Update default bundle to codeql-bundle-v2.26.4</li>
<li><a
href="https://github.com/github/codeql-action/commit/486fec2a3ea2626afcd8c7e9208b4f515078dd7e"><code>486fec2</code></a>
Merge pull request <a
href="https://redirect.github.com/github/codeql-action/issues/4099">#4099</a>
from github/update-supported-enterprise-server-versions</li>
<li><a
href="https://github.com/github/codeql-action/commit/134624c67b20869c2aaa36dafa726375b78a5d76"><code>134624c</code></a>
Merge pull request <a
href="https://redirect.github.com/github/codeql-action/issues/4101">#4101</a>
from github/dependabot/npm_and_yarn/npm-minor-457d82...</li>
<li><a
href="https://github.com/github/codeql-action/commit/ff43db8f982a368288f117354fb8d046e937124c"><code>ff43db8</code></a>
Merge pull request <a
href="https://redirect.github.com/github/codeql-action/issues/4103">#4103</a>
from github/mergeback/v4.37.8-to-main-db488dde</li>
<li><a
href="https://github.com/github/codeql-action/commit/4605e03a74cf891614c4d76f82384a16c1c11816"><code>4605e03</code></a>
Rebuild</li>
<li><a
href="https://github.com/github/codeql-action/commit/099c869cad6bf3b88657154d4ae47ffed27e632d"><code>099c869</code></a>
Update changelog and version after v4.37.8</li>
<li>Additional commits viewable in <a
href="https://github.com/github/codeql-action/compare/ff2f1c621b7f889edc0d3c761ac2e6a3f8cdb0dd...cdf488f595d80d6e07e03d4674febd5ab45fa938">compare
view</a></li>
</ul>
</details>
<br />

Updates `aws-actions/configure-aws-credentials` from 6.2.3 to 6.2.4
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/aws-actions/configure-aws-credentials/releases">aws-actions/configure-aws-credentials's
releases</a>.</em></p>
<blockquote>
<h2>v6.2.4</h2>
<h2><a
href="https://github.com/aws-actions/configure-aws-credentials/compare/v6.2.3...v6.2.4">6.2.4</a>
(2026-08-31)</h2>
<h3>Bug Fixes</h3>
<ul>
<li>account-ids handling, mask proxy as secret in logs (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1943">#1943</a>)
(<a
href="https://github.com/aws-actions/configure-aws-credentials/commit/aa6526434b08748f8776b29964e3f1f5d90e7b63">aa65264</a>)</li>
<li>skip backoff sleep after the final retryAndBackoff attempt (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1937">#1937</a>)
(<a
href="https://github.com/aws-actions/configure-aws-credentials/commit/3852440c21363386b7b790605685d08a7c1a4876">3852440</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/aws-actions/configure-aws-credentials/blob/main/CHANGELOG.md">aws-actions/configure-aws-credentials's
changelog</a>.</em></p>
<blockquote>
<h1>Changelog</h1>
<p>All notable changes to this project will be documented in this file.
See <a
href="https://github.com/conventional-changelog/standard-version">standard-version</a>
for commit guidelines.</p>
<h2><a
href="https://github.com/aws-actions/configure-aws-credentials/compare/v6.2.3...v6.2.4">6.2.4</a>
(2026-08-31)</h2>
<h3>Bug Fixes</h3>
<ul>
<li>account-ids handling, mask proxy as secret in logs (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1943">#1943</a>)
(<a
href="https://github.com/aws-actions/configure-aws-credentials/commit/aa6526434b08748f8776b29964e3f1f5d90e7b63">aa65264</a>)</li>
<li>skip backoff sleep after the final retryAndBackoff attempt (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1937">#1937</a>)
(<a
href="https://github.com/aws-actions/configure-aws-credentials/commit/3852440c21363386b7b790605685d08a7c1a4876">3852440</a>)</li>
</ul>
<h2><a
href="https://github.com/aws-actions/configure-aws-credentials/compare/v6.2.2...v6.2.3">6.2.3</a>
(2026-07-22)</h2>
<h3>Bug Fixes</h3>
<ul>
<li>attach git credentials before Tag Major Version push (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1877">#1877</a>)
(<a
href="https://github.com/aws-actions/configure-aws-credentials/commit/9ae780b171afa8c5a3a6a2d154a765b709492482">9ae780b</a>)</li>
<li>PackedPolicyTooLarge detection in STS tags (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1899">#1899</a>)
(<a
href="https://github.com/aws-actions/configure-aws-credentials/commit/fa8d6a57bbf44b34439fb080bbdadc7c92c285eb">fa8d6a5</a>)</li>
</ul>
<h2><a
href="https://github.com/aws-actions/configure-aws-credentials/compare/v6.2.1...v6.2.2">6.2.2</a>
(2026-07-07)</h2>
<h3>Miscellaneous Chores</h3>
<ul>
<li>release 6.2.2 (<a
href="https://github.com/aws-actions/configure-aws-credentials/commit/d01d678e65d6d2bd9d5ca7a95d6f07b00e25f2c2">d01d678</a>)</li>
</ul>
<h2><a
href="https://github.com/aws-actions/configure-aws-credentials/compare/v6.2.0...v6.2.1">6.2.1</a>
(2026-06-26)</h2>
<h3>Bug Fixes</h3>
<ul>
<li>enforce allowed-account-ids on all auth paths (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1847">#1847</a>)
(<a
href="https://github.com/aws-actions/configure-aws-credentials/commit/4d281fbc56a82e63c3fc14f2cc22361f34c97493">4d281fb</a>)</li>
</ul>
<h2><a
href="https://github.com/aws-actions/configure-aws-credentials/compare/v6.1.3...v6.2.0">6.2.0</a>
(2026-06-01)</h2>
<h3>Features</h3>
<ul>
<li>add additional session tags by default (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1775">#1775</a>)
(<a
href="https://github.com/aws-actions/configure-aws-credentials/commit/e0ba7685077379a14a82d01fefd511490344ebfc">e0ba768</a>)</li>
<li>add more retry logic and better logging (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1764">#1764</a>)
(<a
href="https://github.com/aws-actions/configure-aws-credentials/commit/540d0c13aedb8d55501d220bd2f0b3cdedfe84e8">540d0c1</a>)</li>
<li>add regex validation to role-session-name (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1765">#1765</a>)
(<a
href="https://github.com/aws-actions/configure-aws-credentials/commit/e35449909c6ede5083a48ba4b8bbfaaa1cf09ba1">e354499</a>)</li>
<li>Allow custom session tags to be passed when assuming a role (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1759">#1759</a>)
(<a
href="https://github.com/aws-actions/configure-aws-credentials/commit/61f50f630f383628add73c1eab3f1935ba07da2b">61f50f6</a>)</li>
<li>expose run id in STS client user-agent (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1774">#1774</a>)
(<a
href="https://github.com/aws-actions/configure-aws-credentials/commit/29d1be30273e7ef371d59fccf6ec54572c64ec89">29d1be3</a>)</li>
<li>support custom STS endpoints (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1762">#1762</a>)
(<a
href="https://github.com/aws-actions/configure-aws-credentials/commit/8d52d05d7a4521fa52b39de50cb6114b12e5c332">8d52d05</a>)</li>
</ul>
<h3>Bug Fixes</h3>
<ul>
<li>skip credential check on output-env-credentials: false (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1778">#1778</a>)
(<a
href="https://github.com/aws-actions/configure-aws-credentials/commit/58e7c47adf77846879008deadfeeef8a6969fe6c">58e7c47</a>)</li>
<li>assumeRole failing from session tag size too large (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1808">#1808</a>)
(<a
href="https://github.com/aws-actions/configure-aws-credentials/commit/d6f5dc331b44474b19a52caaf85fa4d637b13c8e">d6f5dc3</a>)</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/aws-actions/configure-aws-credentials/commit/cbe3b392738ccf3f987d68400dafcf4b0624a56c"><code>cbe3b39</code></a>
chore(main): release 6.2.4 (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1942">#1942</a>)</li>
<li><a
href="https://github.com/aws-actions/configure-aws-credentials/commit/58065db07c99675fc21675188b003b7f0b167004"><code>58065db</code></a>
chore(deps): bump js-yaml (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1944">#1944</a>)</li>
<li><a
href="https://github.com/aws-actions/configure-aws-credentials/commit/609df23709e359dc01a42b4c5183ba71167ac38c"><code>609df23</code></a>
chore: Update dist</li>
<li><a
href="https://github.com/aws-actions/configure-aws-credentials/commit/aa6526434b08748f8776b29964e3f1f5d90e7b63"><code>aa65264</code></a>
fix: account-ids handling, mask proxy as secret in logs (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1943">#1943</a>)</li>
<li><a
href="https://github.com/aws-actions/configure-aws-credentials/commit/7fdbbb8968c49fb55011ace47efc7b0ccfc9a28f"><code>7fdbbb8</code></a>
chore: Update dist</li>
<li><a
href="https://github.com/aws-actions/configure-aws-credentials/commit/3852440c21363386b7b790605685d08a7c1a4876"><code>3852440</code></a>
fix: skip backoff sleep after the final retryAndBackoff attempt (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1937">#1937</a>)</li>
<li><a
href="https://github.com/aws-actions/configure-aws-credentials/commit/c16f89bdf4cd065448ea7bde8b96a1dad4c77e41"><code>c16f89b</code></a>
mention renamed repos use the new immutable identifiers (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1941">#1941</a>)</li>
<li><a
href="https://github.com/aws-actions/configure-aws-credentials/commit/9c362eeba7ac7d0419073a8b4af5a83e49e2afaf"><code>9c362ee</code></a>
chore: Update dist</li>
<li><a
href="https://github.com/aws-actions/configure-aws-credentials/commit/d5f8da8822f961cd3016c2cf87aad7e80b40558e"><code>d5f8da8</code></a>
chore(deps): bump <code>@​aws-sdk/client-sts</code> from 3.1111.0 to
3.1116.0 (<a
href="https://redirect.github.com/aws-actions/configure-aws-credentials/issues/1935">#1935</a>)</li>
<li><a
href="https://github.com/aws-actions/configure-aws-credentials/commit/2db24970cf129d7ff6fc04639072bcbe35f8c288"><code>2db2497</code></a>
chore: Update dist</li>
<li>Additional commits viewable in <a
href="https://github.com/aws-actions/configure-aws-credentials/compare/e6de054238d6b7531b4efff3b6587d9aade6a06c...cbe3b392738ccf3f987d68400dafcf4b0624a56c">compare
view</a></li>
</ul>
</details>
<br />

Updates `softprops/action-gh-release` from 3.0.2 to 3.0.3
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/softprops/action-gh-release/releases">softprops/action-gh-release's
releases</a>.</em></p>
<blockquote>
<h2>v3.0.3</h2>
<p><code>3.0.3</code> is a maintenance release with updated
dependencies. It also safely
classifies malformed GitHub API errors to avoid secondary failures (<a
href="https://redirect.github.com/softprops/action-gh-release/issues/822">#822</a>).</p>
<h2>What's Changed</h2>
<h3>Bug fixes 🐛</h3>
<ul>
<li>fix: safely classify GitHub API errors by <a
href="https://github.com/chenrui333"><code>@​chenrui333</code></a> in <a
href="https://redirect.github.com/softprops/action-gh-release/pull/822">softprops/action-gh-release#822</a></li>
</ul>
<h3>Other Changes 🔄</h3>
<ul>
<li>dependency updates</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/softprops/action-gh-release/blob/master/CHANGELOG.md">softprops/action-gh-release's
changelog</a>.</em></p>
<blockquote>
<h2>3.0.3</h2>
<p><code>3.0.3</code> is a maintenance release with updated
dependencies. It also safely
classifies malformed GitHub API errors to avoid secondary failures (<a
href="https://redirect.github.com/softprops/action-gh-release/issues/822">#822</a>).</p>
<h2>What's Changed</h2>
<h3>Bug fixes 🐛</h3>
<ul>
<li>fix: safely classify GitHub API errors by <a
href="https://github.com/chenrui333"><code>@​chenrui333</code></a> in <a
href="https://redirect.github.com/softprops/action-gh-release/pull/822">softprops/action-gh-release#822</a></li>
</ul>
<h3>Other Changes 🔄</h3>
<ul>
<li>dependency updates</li>
</ul>
<h2>3.0.2</h2>
<p><code>3.0.2</code> is a patch release focused on release reliability
and compatibility. It
reuses existing draft releases when publishing prereleases, supports
replacing
release assets on Gitea, hardens streamed asset uploads, and provides
clearer
release-creation diagnostics. It also includes TypeScript, coverage, and
tooling
maintenance merged since <code>3.0.1</code>.</p>
<p>This release fixes <a
href="https://redirect.github.com/softprops/action-gh-release/issues/795">#795</a>,
<a
href="https://redirect.github.com/softprops/action-gh-release/issues/438">#438</a>,
and <a
href="https://redirect.github.com/softprops/action-gh-release/issues/803">#803</a>.
The upload transport hardening covers the
historical failure reported in <a
href="https://redirect.github.com/softprops/action-gh-release/issues/790">#790</a>,
although current hosted Node 24 runners did
not reproduce it naturally. The diagnostics work is related to <a
href="https://redirect.github.com/softprops/action-gh-release/issues/786">#786</a>
and does not
claim a reproducible release-creation fix.</p>
<h2>What's Changed</h2>
<h3>Exciting New Features 🎉</h3>
<ul>
<li>feat: improve release error reporting and test coverage by <a
href="https://github.com/chenrui333"><code>@​chenrui333</code></a> in <a
href="https://redirect.github.com/softprops/action-gh-release/pull/813">softprops/action-gh-release#813</a></li>
</ul>
<h3>Bug fixes 🐛</h3>
<ul>
<li>fix: publish existing draft releases as prereleases by <a
href="https://github.com/godfengliang"><code>@​godfengliang</code></a>
in <a
href="https://redirect.github.com/softprops/action-gh-release/pull/801">softprops/action-gh-release#801</a></li>
<li>fix: upload small checksum assets reliably by <a
href="https://github.com/chenrui333"><code>@​chenrui333</code></a> in <a
href="https://redirect.github.com/softprops/action-gh-release/pull/815">softprops/action-gh-release#815</a></li>
<li>fix: replace existing release assets on Gitea by <a
href="https://github.com/chenrui333"><code>@​chenrui333</code></a> in <a
href="https://redirect.github.com/softprops/action-gh-release/pull/816">softprops/action-gh-release#816</a></li>
<li>fix: clarify release creation 404 errors by <a
href="https://github.com/chenrui333"><code>@​chenrui333</code></a> in <a
href="https://redirect.github.com/softprops/action-gh-release/pull/817">softprops/action-gh-release#817</a></li>
</ul>
<h3>Other Changes 🔄</h3>
<ul>
<li>chore(deps): upgrade TypeScript to 7 by <a
href="https://github.com/chenrui333"><code>@​chenrui333</code></a> in <a
href="https://redirect.github.com/softprops/action-gh-release/pull/812">softprops/action-gh-release#812</a></li>
<li>chore(deps): remove unused TypeScript tooling by <a
href="https://github.com/chenrui333"><code>@​chenrui333</code></a> in <a
href="https://redirect.github.com/softprops/action-gh-release/pull/814">softprops/action-gh-release#814</a></li>
<li>dependency, Node 24 pin, and CI maintenance merged since
<code>3.0.1</code></li>
</ul>
<h2>3.0.1</h2>
<ul>
<li>maintenance release with updated dependencies</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/softprops/action-gh-release/commit/efb35369e0ad2afab669f228072c1b0d510eae64"><code>efb3536</code></a>
release 3.0.3 (<a
href="https://redirect.github.com/softprops/action-gh-release/issues/840">#840</a>)</li>
<li><a
href="https://github.com/softprops/action-gh-release/commit/6441963a7597ab67f36fea0287a7ae58a9bfd8fe"><code>6441963</code></a>
chore(deps): bump the npm group with 2 updates (<a
href="https://redirect.github.com/softprops/action-gh-release/issues/839">#839</a>)</li>
<li><a
href="https://github.com/softprops/action-gh-release/commit/e5ee6bc58a36b838b92fc1217f2e4b414b5abcc8"><code>e5ee6bc</code></a>
chore(deps): bump esbuild from 0.28.1 to 0.28.2 in the npm group (<a
href="https://redirect.github.com/softprops/action-gh-release/issues/837">#837</a>)</li>
<li><a
href="https://github.com/softprops/action-gh-release/commit/d1e66170d32c9ec7bbcb7fae044d3d686ce304d3"><code>d1e6617</code></a>
chore(deps): bump undici from 6.27.0 to 6.28.0 (<a
href="https://redirect.github.com/softprops/action-gh-release/issues/831">#831</a>)</li>
<li><a
href="https://github.com/softprops/action-gh-release/commit/64037519ba20f54c01bc1dc90342c929aac5a2fa"><code>6403751</code></a>
chore(deps): bump the npm group with 2 updates (<a
href="https://redirect.github.com/softprops/action-gh-release/issues/835">#835</a>)</li>
<li><a
href="https://github.com/softprops/action-gh-release/commit/7c7184b6876126a5df15adc5b679dc450a393725"><code>7c7184b</code></a>
chore(deps): bump postcss from 8.5.19 to 8.5.25 (<a
href="https://redirect.github.com/softprops/action-gh-release/issues/833">#833</a>)</li>
<li><a
href="https://github.com/softprops/action-gh-release/commit/0f3f0d2943676d58f9698b3ab590c2056023d77d"><code>0f3f0d2</code></a>
chore(deps): bump brace-expansion from 5.0.8 to 5.0.9 (<a
href="https://redirect.github.com/softprops/action-gh-release/issues/832">#832</a>)</li>
<li><a
href="https://github.com/softprops/action-gh-release/commit/77fb938f2f95e717ce6705d2909af527263360a0"><code>77fb938</code></a>
chore(deps): bump prettier from 3.9.5 to 3.9.6 in the npm group (<a
href="https://redirect.github.com/softprops/action-gh-release/issues/830">#830</a>)</li>
<li><a
href="https://github.com/softprops/action-gh-release/commit/5a6f51711ce2ba103b78f5e9550f810679f11e0e"><code>5a6f517</code></a>
chore(deps): bump brace-expansion from 5.0.7 to 5.0.8 (<a
href="https://redirect.github.com/softprops/action-gh-release/issues/828">#828</a>)</li>
<li><a
href="https://github.com/softprops/action-gh-release/commit/a3c91c98f80000f5b06c7fc0327c54f51c6ab7d8"><code>a3c91c9</code></a>
chore(deps): bump the github-actions group with 2 updates (<a
href="https://redirect.github.com/softprops/action-gh-release/issues/825">#825</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/softprops/action-gh-release/compare/3d0d9888cb7fd7b750713d6e236d1fcb99157228...efb35369e0ad2afab669f228072c1b0d510eae64">compare
view</a></li>
</ul>
</details>
<br />

Updates `linear/linear-release-action` from 0.15.1 to 0.17.1
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/linear/linear-release-action/releases">linear/linear-release-action's
releases</a>.</em></p>
<blockquote>
<h2>v0.17.1</h2>
<h2>What's Changed</h2>
<ul>
<li>Document publish-time version assignment by <a
href="https://github.com/RomainCscn"><code>@​RomainCscn</code></a> in <a
href="https://redirect.github.com/linear/linear-release-action/pull/64">linear/linear-release-action#64</a></li>
<li>Release v0.17.1 by <a
href="https://github.com/RomainCscn"><code>@​RomainCscn</code></a> in <a
href="https://redirect.github.com/linear/linear-release-action/pull/66">linear/linear-release-action#66</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/linear/linear-release-action/compare/v0.17.0...v0.17.1">https://github.com/linear/linear-release-action/compare/v0.17.0...v0.17.1</a></p>
<h2>v0.17.0</h2>
<h2>What's Changed</h2>
<ul>
<li>Release v0.17.0 by <a
href="https://github.com/RomainCscn"><code>@​RomainCscn</code></a> in <a
href="https://redirect.github.com/linear/linear-release-action/pull/63">linear/linear-release-action#63</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/linear/linear-release-action/compare/v0.16.1...v0.17.0">https://github.com/linear/linear-release-action/compare/v0.16.1...v0.17.0</a></p>
<h2>v0.16.1</h2>
<h2>What's Changed</h2>
<ul>
<li>Verify downloaded CLI artifacts before execution by <a
href="https://github.com/RomainCscn"><code>@​RomainCscn</code></a> in <a
href="https://redirect.github.com/linear/linear-release-action/pull/60">linear/linear-release-action#60</a></li>
<li>Authenticate the CI install test's GitHub API calls by <a
href="https://github.com/RomainCscn"><code>@​RomainCscn</code></a> in <a
href="https://redirect.github.com/linear/linear-release-action/pull/62">linear/linear-release-action#62</a></li>
<li>Release v0.16.1 by <a
href="https://github.com/RomainCscn"><code>@​RomainCscn</code></a> in <a
href="https://redirect.github.com/linear/linear-release-action/pull/61">linear/linear-release-action#61</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/linear/linear-release-action/compare/v0.16.0...v0.16.1">https://github.com/linear/linear-release-action/compare/v0.16.0...v0.16.1</a></p>
<p><strong>Note:</strong> <code>cli_version: latest</code> now resolves
the release through the GitHub API, which requires <code>jq</code> and a
token. Both are present on GitHub-hosted runners; minimal self-hosted
runners without <code>jq</code> will fail with a clear error.</p>
<h2>v0.16.0</h2>
<h2>What's Changed</h2>
<ul>
<li>Release v0.16.0 by <a
href="https://github.com/axelniklasson"><code>@​axelniklasson</code></a>
in <a
href="https://redirect.github.com/linear/linear-release-action/pull/58">linear/linear-release-action#58</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/linear/linear-release-action/compare/v0.15.1...v0.16.0">https://github.com/linear/linear-release-action/compare/v0.15.1...v0.16.0</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/linear/linear-release-action/commit/3f31fcf14c110cc53579fcc3575a26d469c413b4"><code>3f31fcf</code></a>
Release v0.17.1 (<a
href="https://redirect.github.com/linear/linear-release-action/issues/66">#66</a>)</li>
<li><a
href="https://github.com/linear/linear-release-action/commit/cbf1f6d901dfb52fe08cfc21ce324ab202041c7e"><code>cbf1f6d</code></a>
Document publish-time version assignment (<a
href="https://redirect.github.com/linear/linear-release-action/issues/64">#64</a>)</li>
<li><a
href="https://github.com/linear/linear-release-action/commit/e1ca7cace602cb66768264790a2b316630877148"><code>e1ca7ca</code></a>
Release v0.17.0 (<a
href="https://redirect.github.com/linear/linear-release-action/issues/63">#63</a>)</li>
<li><a
href="https://github.com/linear/linear-release-action/commit/7d7409a01ea2391b4a2661be791f59a788cbbe42"><code>7d7409a</code></a>
Release v0.16.1 (<a
href="https://redirect.github.com/linear/linear-release-action/issues/61">#61</a>)</li>
<li><a
href="https://github.com/linear/linear-release-action/commit/9589057a3f4a501dacab6426f2a738925199b19f"><code>9589057</code></a>
Authenticate the CI install test's GitHub API calls (<a
href="https://redirect.github.com/linear/linear-release-action/issues/62">#62</a>)</li>
<li><a
href="https://github.com/linear/linear-release-action/commit/fc505cbc7bb303412a3af89da96c0f3c348068cd"><code>fc505cb</code></a>
Verify future CLI release artifacts before execution (<a
href="https://redirect.github.com/linear/linear-release-action/issues/60">#60</a>)</li>
<li><a
href="https://github.com/linear/linear-release-action/commit/0a25abab892a91062ebf42260dbb2ce6277aa205"><code>0a25aba</code></a>
Release v0.16.0 (<a
href="https://redirect.github.com/linear/linear-release-action/issues/58">#58</a>)</li>
<li>See full diff in <a
href="https://github.com/linear/linear-release-action/compare/17b8c24f8ceb2b98cabaf1965ff83c55dd596fac...3f31fcf14c110cc53579fcc3575a26d469c413b4">compare
view</a></li>
</ul>
</details>
<br />


Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@supabase-cli-releaser
chore: sync API types from infrastructure (#6488)
e6fa648 
This PR was automatically created to sync API types from the
infrastructure repository.

Changes were detected in the generated API code after syncing with the
latest spec from infrastructure.

Co-authored-by: supabase-cli-releaser[bot] <246109035+supabase-cli-releaser[bot]@users.noreply.github.com>
@Coly010
fix(cli): hedge config's 404 message, align push load errors (#6490)
3343c2f 
## What changed

- `config push`'s 404 read-status message (shared with `config
diff`/`config pull`, since all three read `GET
/v2/projects/{ref}/config`) now names the resolved API host and hedges
that this v2 endpoint may not be served there, instead of only
suggesting a wrong project ref.
- Hoisted `config diff`/`config pull`'s shared local-config-load helper
(parse-error file naming, duplicate-remote message, missing-file
pointing at `supabase init`) into a new `config.load.ts`, and switched
`config push` to use it — replacing its own hardcoded `config.toml`-only
messages.

## Why

Two DX follow-ups from the CLI-2313 review, deferred because each
changes an established, test-pinned string:
[CLI-2321](https://linear.app/supabase/issue/CLI-2321).

## User-facing text changes

- `config push`/`config diff`/`config pull`'s 404 message changed from
`Project <ref> not found. Check the project ref, or run \`supabase
projects list\`...` to `Could not read configuration for project <ref>
(404). Check the project ref with \`supabase projects list\`; if the ref
is correct, this Supabase API endpoint may not be available at <api
host>.`
- `config push`'s local-config-load failure messages now match `config
diff`/`config pull`'s established shape (correct file name on parse
failure, `Run \`supabase init\` to create one.` on a missing file).
depthfirst-app[bot]
depthfirst-app Bot reviewed Sep 7, 2026
View reviewed changes
Comment thread .github/ai-review/adjudicate-prompt.md
@@ -0,0 +1,80 @@
# AI code review — adjudication pass

> **Prompt-injection guard:** The PR title, body, diff, code, code comments,

@depthfirst-app depthfirst-app Bot Sep 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Severity: MEDIUM

The PR title, body, diff, and files are attacker-controlled inputs to the adjudicator. This instruction-only guard does not prevent prompt injection from causing the model to omit a finding or mark a real vulnerability refuted; that verdict then flows into the posted security review without an independent completeness check.
Helpful? Add 👍 / 👎

💡 Fix Suggestion

Suggestion: The instruction-only guard at lines 3–8 cannot reliably prevent a prompt-injection attack from causing the adjudicator to suppress or alter findings, because the model's own output is the only enforcement mechanism. To harden this pipeline with an independent, out-of-band completeness check: (1) In post-review.ts's validate-merged command, after parsing the merged review, load /tmp/ai-review/claude-findings.json and /tmp/ai-review/codex-findings.json, count their findings independently, and assert that merged.stats.claude_total and merged.stats.codex_total match those externally-computed counts — this prevents a prompt-injected model from quietly under-reporting totals to hide dropped findings. (2) Optionally also verify that the number of merged findings is at least max(claude_total, codex_total) (since deduplication can only reduce the count, not produce fewer entries than the larger single-model set). (3) For structural prompt hardening, wrap all untrusted content (diff, PR metadata, finding JSON files) in XML-style delimiter tags (e.g. <untrusted-data>…</untrusted-data>) when constructing the final prompt context, rather than relying solely on natural-language instructions to separate data from directives. These changes are independent of the prompt text and enforce correctness at the validation layer where the LLM cannot interfere.

Comment thread .github/workflows/ai-review.yml
# its output file — the step sits idle until the job timeout, discarding
# a completed review (openai/codex-action#150). v1.11 handles the same
# heavy workload cleanly. There is no released fix above v1.12 yet.
uses: openai/codex-action@86365089eb2b84e0a8fb0717b304f8bdcb13b20e # v1.12

@depthfirst-app depthfirst-app Bot Sep 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚪ Severity: LOW

This pins Codex v1.12 even though the surrounding workflow says v1.11 is required because v1.12 can hang after heavy turns. A canceled independent or adjudication run prevents the downstream adjudication/post jobs, so a large or complex PR can cause the security review and its findings to be silently unavailable.
Helpful? Add 👍 / 👎

💡 Fix Suggestion

Suggestion: Replace the v1.12 commit hash on line 334 with the correct v1.11 commit hash. The surrounding comment (lines 329–333) already documents that v1.11 must be used because v1.12 has a confirmed regression (openai/codex-action#150) where heavy runs hang indefinitely and silently discard completed review output. Look up the full 40-character SHA for the v1.11 tag in the openai/codex-action repository (the hash prefix 52fe01ec is referenced in the safety-strategy comment at line 324 and is likely the v1.11 pin). Replace uses: openai/codex-action@86365089eb2b84e0a8fb0717b304f8bdcb13b20e # v1.12 with uses: openai/codex-action@<full-v1.11-sha> # v1.11. The same incorrect v1.12 hash also appears at line 498 for the adjudication step and should be updated identically.

Coly010 and others added 4 commits September 7, 2026 10:56
@Coly010
fix(cli): confine auth email content_path to project root (CLI-2320) (#…
ad95a9a 
…6489)

## Summary

`config push` resolves `auth.email.template.*.content_path` and
`auth.email.notification.*.content_path` from disk before uploading
their
bytes as part of the auth config write. Resolution previously joined a
relative path onto the project root (or passed an absolute path through
unchanged) with no containment check, so a crafted `content_path` could
resolve outside the project. `content_path` is now confined to the
project
root: any resolved path — a relative `..` escape or an absolute path
elsewhere on disk — aborts before the file is read, using the existing
`Invalid config for auth.email.<kind>.<name>.content_path: <reason>`
error
shape.

Linear: CLI-2320 (surfaced by CLI-2313's security review; intentionally
kept
out of that PR).

## What changed

- `push.auth-email-content.ts` — new `resolveContainedContentPath`
normalizes
the candidate path with `path.resolve` and rejects anything outside the
  discovered project root before `readTemplateContent` runs;
`legacyLoadAuthEmailContent`'s template and notification loops both
route
  through it. The existing notification legacy-fallback behavior
(`supabase/`-relative lookup) is preserved as long as the resolved
result
  stays inside the root.
- `push.auth-email-content.unit.test.ts` — new coverage: absolute path
outside
  root (template + notification), relative `..` escape (template +
  notification), and a boundary case for a path resolving to exactly the
  project root.
- `SIDE_EFFECTS.md` — documents the containment rule in Files Read,
Notes, and
  the exit-code table.
@Coly010
refactor(config): consolidate command-family helpers (CLI-2292) (#6491)
8773536 
## Current Behavior

Follow-up debt recorded by the CLI-2064 architecture review (explicitly
ruled a follow-up, not a pre-merge fix):

1. `pathKey` has separate definitions across the config command family's
`pull/` modules; `deepEqualValue`/`valueAtPath`/`isDeclaredAtPath` are
each implemented twice (`pull.plan.ts`); `deepSetAtPath` is a third
deep-set concept, only reachable through the planner.
2. `LegacyConfigTargetErrors<A,B,C,D,E>` in `config.target.ts`
hand-injects five generic constructors per command, and reclassifies a
404 via a `Predicate.hasProperty("status")` duck-type check.
3. `config diff` and `config pull` render change classes through a
shared label map in `config.format.ts`.
4. `config-edit.ts`'s `[remotes.<label>]` placement logic hardcodes the
`"remotes"`/`"project_id"` literals inline at each use site.

## Expected Behavior

1. One `config.paths.ts` at the command family root holds the shared
path/value helpers; the three `pull/` modules that duplicated them now
import from it. `config-edit.ts` (in `@supabase/config`, pinned to
`smol-toml` as its only import per ADR 0023) keeps its own independent
copies — deliberately out of scope.
2. `config.target.ts` now mints each family's four target-resolution
error classes from a prefix (`legacyMintConfigTargetErrors`) and builds
their shared message-template bundle in one place
(`legacyConfigTargetErrorsFor`), collapsing
`LegacyConfigTargetErrors`/`legacyResolveConfigTarget` from five
generics to two and replacing the duck-typed 404 check with a typed
`LegacyConfigTargetResolveFailure` bound. `diff`, `pull`, and `push` now
all route through this factory — `push` adopted the shared resolver
since the CLI-2064 review, meeting the precondition this item was
waiting on.
3. Already done in #6454 (CLI-2313) — `diff.format.ts` already renders
through `config.format.ts`'s shared label map. No changes needed;
confirmed while implementing this issue.
4. `config-edit.ts` now names the two literals (`REMOTES_TABLE_NAME`,
`REMOTE_PROJECT_ID_KEY`) and a shared `isRemotesLabelRoot` predicate
next to the doc comment that already describes the exception.

No user-observable behavior changes — every renamed/relocated helper
keeps its exact prior implementation, and the four minted error classes
keep their original tags, actionability, and message text (verified
against the existing `diff`/`pull`/`push` integration test suites and
the `error-actionability-coverage` drift guard).
@avallete @claude @cursoragent
feat(cli): make the bundled pg-delta engine the only pg-delta impleme…
3095e91 
…ntation (#6487)

## Summary

First half of the pg-delta cleanup, tracked as
[CLI-2211](https://linear.app/supabase/issue/CLI-2211). The second half
(flipping the default engine to pg-delta, CLI-1588) is stacked on top of
this PR in [#6391](#6391).

The `SUPABASE_USE_PG_DELTA_NEXT` escape hatch shipped in v2.115.0 as a
temporary opt-out back to the legacy edge-runtime pg-delta engine; its
release notes announced removal after ~a month. Setting it now has no
effect: the in-process `@supabase/pg-delta` engine is the only pg-delta
implementation.

Deleted with the legacy engine:

- the flag module and the engine selector layer; `LegacyPgDeltaEngine`
loses its `implementation` discriminator and every handler branch keyed
on it
- the edge-runtime pg-delta Deno script templates, the
`supabase/.temp/pgdelta-version` npm pin, and the `PGDELTA_NPM_REGISTRY`
/ `PGDELTA_{SOURCE,TARGET}_SSLROOTCERT` plumbing (all
legacy-engine-only; the edge-runtime service itself stays — migra still
runs through it)
- the migrations-catalog cache warmups after `db push` / `db reset` /
`start` / `db start` / bootstrap (TypeScript and Go), and the whole
catalog snapshot machinery (`legacy-pgdelta.cache.ts`); the shared
migration lister moves to `command-internal/legacy-migration-list.ts`
- the legacy declarative catalog seam
(`LegacyDeclarativeSeam.exportCatalog`), the declarative-apply engine
(`legacy-pgdelta.apply.ts`), and `db pull`'s legacy empty-diff debug
bundle
- the "`--strict-coverage` has no effect with the legacy pg-delta
engine" warning — the flag is now always effective
- leftover writer/debug/edge-runtime surface that only the deleted
engine used (manifest-less wipe-and-rewrite, orphan debug-bundle fields,
`extraFiles` / `extraEnv`)

`db pull --experimental` and `db remote commit` now run in-process as
well (commit is a thin `db pull` wrapper with a fixed `remote_commit`
name and the cobra deprecation line). The deprecated `--experimental`
export writes the same declarative tree as `--declarative`.

Go is slimmed to match: `db pull`, `db dump`, `db remote commit`, and
the Go pg-delta / dump engines are gone. `supabase-go db diff` only
serves the TypeScript `--use-pg-schema` proxy. `db remote changes` still
uses Go migra.

Also bumps `@supabase/pg-delta` to `1.0.0-alpha.49` (same
`@supabase/pg-topo 1.0.0-alpha.6` peer; the release is younger than the
workspace's minimum release age, so it is on the exclusion list).

**Engine selection is unchanged in this PR**: migra stays the default
for `db diff` / migration-style `db pull`, and pg-delta is still opted
into through `[experimental.pgdelta] enabled = true`,
`SUPABASE_EXPERIMENTAL_PG_DELTA`, `--use-pg-delta`, or `--diff-engine
pg-delta`. An absent `[experimental.pgdelta]` section still resolves
`enabled = false`, so declarative export still writes
`[db.migrations].schema_paths` in that default case. SIDE_EFFECTS.md
files, the `db pull` docs, and the Go CONTRIBUTING pg-delta section were
updated to match.

## Linked issue

Linear: [CLI-2211](https://linear.app/supabase/issue/CLI-2211)

- [x] The linked issue is **open** and carries the
`open-for-contribution` label (or I'm a Supabase maintainer).

## Checklist

- [x] The PR title follows [Conventional
Commits](https://www.conventionalcommits.org/) (e.g. `fix(cli): …`).
- [x] Tests added or updated for the change.
- [x] From the repository root, `pnpm check:all` passes; relevant
package tests pass for every touched workspace, and `pnpm types:check`
passes for each touched TypeScript workspace (or workspace declaring
it).

---------

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@avallete
ci: generate large AI review diffs locally (#6493)
c4fe9c7 
## Summary

Generate AI-review diffs locally from trusted, full-history Git
checkouts instead of GitHub’s size-capped PR diff endpoint. A shared
helper now serves the Claude, Codex, and adjudication stages while
preserving triple-dot merge-base semantics.

Add regression coverage for diffs beyond 20,000 lines and for diverged
base/head histories.

## Why

[AI Review run
34116168817](https://github.com/supabase/cli/actions/runs/34116168817)
failed before either reviewer started because GitHub returned HTTP 406
once PR #6487 exceeded the endpoint’s 20,000-line limit.
@avallete

avallete commented Sep 7, 2026

Copy link
Copy Markdown
Member

/ai-review

7ttp added 2 commits September 7, 2026 14:19
@7ttp
fix(cli): honor SUPABASE_API_* overrides (CLI-2318) (#6467)
6689867 
## TL;DR

fixes `seed buckets`, `db reset`, and `storage --local` ignoring the
`SUPABASE_API_*` overrides and calling the local storage gateway on the
raw `config.toml` port...

## whats broken?

`SUPABASE_API_PORT=54331 supabase seed buckets` fails with a transport
error on `http://127.0.0.1:54321/storage/v1/bucket`
the shared credentials resolver reads `api.port`, `api.external_url`,
and `api.tls.*` raw, while `start`/`status`/`stop` resolve the same
fields post-override. the CLI can start a stack it then cannot reach.

## now fixed by:

folding the `SUPABASE_API_*` overrides once in `resolveLocalApiConfig` 
thru the same `legacyEnvOverride*` helpers and dotenv walk the sibling
commands use
so the gateway URL and TLS gate read the resolved view. a malformed
override now fails with the same invalid config error
`start`/`status`/`stop` already raise. `--linked` untouched...

## ref:

- closes: #6452
@7ttp
test(cli): cover config push and unlink (CLI-2293, CLI-2326) (#6494)
21db855 
## TL;DR

adds live e2e coverage for `config push` and `unlink`, closing the last
gaps in the config and link command families

## whats introduced?

- `config push`: declares a single `api.max_rows` value in a sparse
config.toml, pushes it, proves convergence
`config diff`, then restores the captured value with a re-proven push in
the same test
- `unlink`: links the suite project for real, unlinks it, and proves the
workspace is left with no local link state

## ref:

- closes: CLI-2293 &  CLI-2326
- passed here:
https://github.com/supabase/cli/actions/runs/34119883928/job/101735308268
@supabase-cli-releaser
supabase-cli-releaser Bot merged commit 21db855 into main Sep 7, 2026
46 of 47 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@depthfirst-app depthfirst-app[bot] depthfirst-app[bot] left review comments
@avallete avallete avallete approved these changes
+2 more reviewers
@github-advanced-security github-advanced-security[bot] github-advanced-security[bot] left review comments
@chatgpt-codex-connector chatgpt-codex-connector[bot] chatgpt-codex-connector[bot] left review comments
Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

do not merge Approve to apply; do not merge.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.