chore: production deploy by supabase-cli-releaser[bot] · Pull Request #6321 · supabase/cli

supabase-cli-releaser · 2026-08-25T02:29:42Z

fix(stack): deflake service-state settling and control endpoint acquisition (fix(stack): deflake service-state settling and control endpoint acquisition #6245)
test: deflake more flaky suites (test: deflake more flaky suites #6248)
fix(cli): restore postgres after role reverts (CLI-2205) (fix(cli): restore postgres after role reverts (CLI-2205) #6246)
chore: sync API types from infrastructure (chore: sync API types from infrastructure #6251)
fix(deps): bump the go-minor group across 1 directory with 2 updates (fix(deps): bump the go-minor group across 1 directory with 2 updates #6256)
fix(deps): bump the npm-major group with 5 updates (fix(deps): bump the npm-major group with 5 updates #6259)
fix(cli): stream edge runtime bootstrap (CLI-2216) (fix(cli): stream edge runtime bootstrap (CLI-2216) #6273)
chore(api): sync Management API OpenAPI spec (chore(api): sync Management API OpenAPI spec #6272)
fix(cli): run DROP INDEX CONCURRENTLY outside the migration transaction (CLI-2218) (fix(cli): run DROP INDEX CONCURRENTLY outside the migration transaction (CLI-2218) #6276)
ci: run the develop CI suite on stacked and draft PRs via a run-ci label (ci: run the develop CI suite on stacked and draft PRs via a run-ci label #6275)
chore(ci): bump the actions-major group with 3 updates (chore(ci): bump the actions-major group with 3 updates #6279)
test(stack): deflake readiness (test(stack): deflake readiness #6282)
docs(cli): make the TS legacy shell the source of truth in agent instructions (docs(cli): make the TS legacy shell the source of truth in agent instructions #6281)
fix(cli): clamp edge-runtime nofile ulimit to the host hard limit (fix(cli): clamp edge-runtime nofile ulimit to the host hard limit #6284)
chore(api): sync Management API OpenAPI spec (chore(api): sync Management API OpenAPI spec #6280)
fix(deps): bump the npm-major group with 7 updates (fix(deps): bump the npm-major group with 7 updates #6278)
fix(cli): bypass loopback proxying (fix(cli): bypass loopback proxying (CLI-2034) #6283)
fix(deps): bump golang.org/x/mod from 0.39.0 to 0.40.0 in /apps/cli-go/pkg in the go-minor group across 1 directory (fix(deps): bump golang.org/x/mod from 0.39.0 to 0.40.0 in /apps/cli-go/pkg in the go-minor group across 1 directory #6285)
chore(deps): consolidate TypeScript and update Effect (chore(deps): consolidate TypeScript and update Effect #6289)
fix(deps): bump the npm-major group across 1 directory with 6 updates (fix(deps): bump the npm-major group across 1 directory with 6 updates #6291)
chore: update Bun to 1.4.0 (chore: update Bun to 1.4.0 #6293)
chore(api): sync Management API OpenAPI spec (chore(api): sync Management API OpenAPI spec #6288)
fix(docker): bump supabase/postgres from 17.6.1.159 to 17.6.1.165 in /apps/cli-go/pkg/config/templates (fix(docker): bump supabase/postgres from 17.6.1.159 to 17.6.1.165 in /apps/cli-go/pkg/config/templates #6258)
fix(docker): bump the docker-minor group in /apps/cli-go/pkg/config/templates with 4 updates (fix(docker): bump the docker-minor group in /apps/cli-go/pkg/config/templates with 4 updates #6257)
feat(stack): prepare slim resources on demand (feat(stack): prepare slim resources on demand #6250)
fix(deps): bump github.com/posthog/posthog-go from 1.23.0 to 1.23.1 in /apps/cli-go in the go-minor group across 1 directory (fix(deps): bump github.com/posthog/posthog-go from 1.23.0 to 1.23.1 in /apps/cli-go in the go-minor group across 1 directory #6297)
fix(deps-dev): bump the npm-major group with 3 updates (fix(deps-dev): bump the npm-major group with 3 updates #6299)
fix(deps): bump the npm-major group with 2 updates (fix(deps): bump the npm-major group with 2 updates #6301)
feat(cli): upgrade pg-delta next to alpha.46 (feat(cli): upgrade pg-delta next to alpha.46 #6300)
test(cli): collocate live e2e coverage (test(cli): collocate live e2e coverage #6294)
ci(cli): publish ts docs reference (ci(cli): publish ts docs reference (CLI-2171) #6253)
feat(config): expose config defaults and provide sparse mapping functions (feat(config): expose config defaults and provide sparse mapping functions #6205)
feat(cli): cache the shadow database baseline as a PGDATA snapshot (CLI-2191) (feat(cli): cache the shadow database baseline as a PGDATA snapshot (CLI-2191) #6184)
test(cli): stabilize e2e shard one (test(cli): stabilize e2e shard one #6313)
fix(cli): mount external scope targets (fix(cli): mount external scope targets #6309)
chore(ci): bump docker/setup-buildx-action from 4.2.0 to 4.3.0 in the actions-major group (chore(ci): bump docker/setup-buildx-action from 4.2.0 to 4.3.0 in the actions-major group #6307)
fix(deps): bump github.com/oapi-codegen/runtime from 1.6.0 to 1.7.0 in /apps/cli-go in the go-minor group across 1 directory (fix(deps): bump github.com/oapi-codegen/runtime from 1.6.0 to 1.7.0 in /apps/cli-go in the go-minor group across 1 directory #6306)
fix(deps): bump github.com/getkin/kin-openapi from 0.136.0 to 0.144.0 in /apps/cli-go (fix(deps): bump github.com/getkin/kin-openapi from 0.136.0 to 0.144.0 in /apps/cli-go #6316)
fix(deps): bump the go-minor group across 2 directories with 1 update (fix(deps): bump the go-minor group across 2 directories with 1 update #6318)

…sition (#6245) ## Summary This PR removes a family of intermittent stack test failures by fixing the underlying races rather than the tests, then verifies the result with five consecutive green CI runs and a local 2× CPU-oversubscribed stress gauntlet (8/8 integration runs green). Runtime fixes: - **`stopService` settling race** (the original `'Dormant' vs 'Stopped'` CI flake): `stopService` returned before the background projection fiber re-published the public state, so an immediate `getState` could observe the previous status. It now settles the projection before returning, matching every start path. - **Control endpoint port collisions**: the control endpoint derived a single loopback port from two bytes of the stack id, so two live stacks could birthday-collide and the later acquirer hard-failed with `ControlAddressConflictError`. `acquireControl`/`probeControl` now walk a short deterministic candidate sequence — attach to a matching owner on any candidate (verified by `ownershipId`), bind the first free one, and conflict only when all candidates are foreign-occupied. `connectManagedStack` uses the probed endpoint, and exact service-port requests reserve every candidate. Protocol mismatch still fails closed. - **Keep-alive livelock**: control status probes reused pooled connections, so a closed listener kept answering `/owner` on the poller's own hot connection and a scan-first acquirer could never bind the freed endpoint. Control reads and stop requests are now one-shot connections in both Node and Bun transports. - **Retry budgets**: the bound-but-not-serving acquire retry is now duration-bounded (a count-based budget stretched a single acquire to 30–45s when reads hit the 500ms transport timeout), and `startStack`'s workspace-repair fence waits up to 30s instead of ~5s, which a realistic Git repair can exceed. Test hardening: - Managed test layers set a new `preferCatalogDefaults: false` plan option so parallel suites stop contending on the default ports (54321…), which sticky reuse re-reserves exactly; production behavior and the spec'd no-relocation semantics are unchanged. - Write-failure injections are privilege-independent (FileSystem-seam gates / directory-as-file instead of chmod, which root bypasses). - Supervisor test watchers re-arm on ENOENT from atomic-write temp files vanishing mid-scan; sub-second synchronization timeouts are widened into guards. ## 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. - [x] `pnpm check:all` and `pnpm test` pass for the workspace(s) I touched. https://claude.ai/code/session_01McsNM9yxC5tiY6SusBALoq --------- Co-authored-by: Claude <noreply@anthropic.com>

## TL;DR Replaces every fixed attempt-count retry budget in tests with wall-clock deadlines, retries managed control acquisition with a fresh workspace when the identity-derived port collides with a concurrent stack's live control server and makes the attempt count as "rule" in AGENTS.md .... ## ref: - fixes the supervisor fake-owner bind flake https://github.com/supabase/cli/actions/runs/32117291754/job/95649578844 - & the managed manager-ports conflict flake https://github.com/supabase/cli/actions/runs/32117383408/job/95656435059 --------- Co-authored-by: Andrew Valleteau <avallete@users.noreply.github.com>

## TL;DR Passwordless `db push --linked` breaks on any migration containing `reset role`: the login role path relies on a session level `SET SESSION ROLE postgres` that the migration itself undoes. File runners now re-assert the step-down immediately after each role-reverting statement, at the end of each file, and before every CLI owned ledger write, so the whole file behaves the same on both auth paths. ## whats biting? The passwordless path connects as a temp `cli_login_*` role and steps down to `postgres` once at connect. A migration's `reset role` reverts the session to the login role, so: - the appended history insert fails with `permission denied for schema supabase_migrations (SQLSTATE 42501)` and rolls the migration back, even though every user statement succeeded - authored transaction and pg-delta no-transaction files commit their statements but never record, so the next push re-applies them - statements between the `reset role` and the end of the same file run as the login role, so `granted by current_user` cleanup silently no-ops while the push exits 0 (reproduced on staging: the stale `pg_auth_members` grant survives) - later files and the `seed_files` upsert run as the login role too ## fixed now by: - `LegacyDbSession.restoreRoleSql` (set only when the step-down ran) is injected by every file runner right after each top-level role revert (`RESET ROLE`, `SET [SESSION] ROLE [TO|=] NONE|DEFAULT` including a case-sensitively quoted `'none'`, `RESET SESSION AUTHORIZATION`, `SET SESSION AUTHORIZATION DEFAULT`, `DISCARD ALL`), and again at end of file and before the history insert and both `seed_files` upserts, so `current_user` matches a password session for the whole file - injected restores never shift `At statement: N` and are never recorded in the history row; deliberate `set role <x>` choreography is untouched, and password, local and plain `--db-url` sessions see a byte identical statement stream - the residual (dynamic SQL, `SET LOCAL ROLE NONE`, `session_user` itself) is documented in `docs/go-cli-divergences.md` with the end-of-file restore protecting every CLI owned write; both `SIDE_EFFECTS.md` tables record the new statements ## ref: - closes: #6236

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>

Bumps the npm-major group with 5 updates: | Package | From | To | | --- | --- | --- | | [smol-toml](https://github.com/squirrelchat/smol-toml) | `1.7.1` | `1.8.0` | | [@supabase/supabase-js](https://github.com/supabase/supabase-js/tree/HEAD/packages/core/supabase-js) | `2.112.2` | `2.112.3` | | [@anthropic-ai/claude-agent-sdk](https://github.com/anthropics/claude-agent-sdk-typescript) | `0.3.227` | `0.3.228` | | [@vercel/detect-agent](https://github.com/vercel/vercel/tree/HEAD/packages/detect-agent) | `1.2.4` | `1.2.5` | | [knip](https://github.com/webpro-nl/knip/tree/HEAD/packages/knip) | `6.32.1` | `6.32.2` | Updates `smol-toml` from 1.7.1 to 1.8.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/squirrelchat/smol-toml/releases">smol-toml's releases</a>.</em></p> <blockquote> <h2>v1.8.0</h2> <h2>What's Changed</h2> <ul> <li>feat: stringify temporal objects by <a href="https://github.com/Gouvernathor"><code>@Gouvernathor</code></a> and <a href="https://github.com/cyyynthia"><code>@cyyynthia</code></a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/squirrelchat/smol-toml/compare/v1.7.2...v1.8.0">https://github.com/squirrelchat/smol-toml/compare/v1.7.2...v1.8.0</a></p> <h2>v1.7.2</h2> <h2>What's Changed</h2> <ul> <li>refactor: improve performance of the parser by <a href="https://github.com/cyyynthia"><code>@cyyynthia</code></a></li> <li>chore: revert sourcemap publishing by <a href="https://github.com/cyyynthia"><code>@cyyynthia</code></a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/squirrelchat/smol-toml/compare/v1.7.1...v1.7.2">https://github.com/squirrelchat/smol-toml/compare/v1.7.1...v1.7.2</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/squirrelchat/smol-toml/commit/6d0f4774700c40ce8b5794934eb771870a9a93d3"><code>6d0f477</code></a> chore: bump version</li> <li><a href="https://github.com/squirrelchat/smol-toml/commit/97e9713e03fa382ccfad0c2289be03456a15ca98"><code>97e9713</code></a> docs: mention temporal api</li> <li><a href="https://github.com/squirrelchat/smol-toml/commit/7a3068d0200214c902ee65a3962940a36312fe79"><code>7a3068d</code></a> perf: ubench opt for <code>instanceof Date</code></li> <li><a href="https://github.com/squirrelchat/smol-toml/commit/7e8c09ad9d8b77e88f9f1a59034c99b1ce484be6"><code>7e8c09a</code></a> feat: stringify temporal</li> <li><a href="https://github.com/squirrelchat/smol-toml/commit/19239d0e00e63eead644955e896f327b8ac3e21c"><code>19239d0</code></a> chore: bump version</li> <li><a href="https://github.com/squirrelchat/smol-toml/commit/5f55c3aeb90e84e48fbfe6db504a37ecc2f9314a"><code>5f55c3a</code></a> chore: revert sourcemap publishing</li> <li><a href="https://github.com/squirrelchat/smol-toml/commit/5c26f1ba1a126c2691f9e5cf12d2bfc520f2ae94"><code>5c26f1b</code></a> chore: update benchmarks</li> <li><a href="https://github.com/squirrelchat/smol-toml/commit/92832d29eadef634c9b87e37c9f0a56aa1f30fa0"><code>92832d2</code></a> refactor: better logic orchestration in structs</li> <li><a href="https://github.com/squirrelchat/smol-toml/commit/2fb9ab871e6d30bce4118a2917320a3f44a3ec4c"><code>2fb9ab8</code></a> refactor: ctx object instead of pointer arg + tuple returns</li> <li><a href="https://github.com/squirrelchat/smol-toml/commit/e6017c4fd9e894a33af1545d2c4c51e2b4a7c9ce"><code>e6017c4</code></a> ci: use staged publish</li> <li>See full diff in <a href="https://github.com/squirrelchat/smol-toml/compare/v1.7.1...v1.8.0">compare view</a></li> </ul> </details> <br /> Updates `@supabase/supabase-js` from 2.112.2 to 2.112.3 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/supabase/supabase-js/releases">@supabase/supabase-js's releases</a>.</em></p> <blockquote> <h2>v2.112.3</h2> <h2>2.112.3 (2026-08-11)</h2> <h3>🩹 Fixes</h3> <ul> <li><strong>supabase:</strong> add trace context headers to canonical CORS allow-list (<a href="https://redirect.github.com/supabase/supabase-js/pull/2603">#2603</a>)</li> <li><strong>supabase:</strong> improve trace propagation sampling and diagnostics (<a href="https://redirect.github.com/supabase/supabase-js/pull/2604">#2604</a>)</li> </ul> <h3>❤️ Thank You</h3> <ul> <li>Katerina Skroumpelou <a href="https://github.com/mandarini"><code>@mandarini</code></a></li> </ul> <h2>v2.112.3-canary.0</h2> <h2>2.112.3-canary.0 (2026-08-11)</h2> <h3>🩹 Fixes</h3> <ul> <li><strong>supabase:</strong> add trace context headers to canonical CORS allow-list (<a href="https://redirect.github.com/supabase/supabase-js/pull/2603">#2603</a>)</li> <li><strong>supabase:</strong> improve trace propagation sampling and diagnostics (<a href="https://redirect.github.com/supabase/supabase-js/pull/2604">#2604</a>)</li> </ul> <h3>❤️ Thank You</h3> <ul> <li>Katerina Skroumpelou <a href="https://github.com/mandarini"><code>@mandarini</code></a></li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/supabase/supabase-js/blob/master/packages/core/supabase-js/CHANGELOG.md">@supabase/supabase-js's changelog</a>.</em></p> <blockquote> <h2>2.112.3 (2026-08-11)</h2> <h3>🩹 Fixes</h3> <ul> <li><strong>supabase:</strong> improve trace propagation sampling and diagnostics (<a href="https://redirect.github.com/supabase/supabase-js/pull/2604">#2604</a>)</li> <li><strong>supabase:</strong> add trace context headers to canonical CORS allow-list (<a href="https://redirect.github.com/supabase/supabase-js/pull/2603">#2603</a>)</li> </ul> <h3>❤️ Thank You</h3> <ul> <li>Katerina Skroumpelou <a href="https://github.com/mandarini"><code>@mandarini</code></a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/supabase/supabase-js/commit/e44447c2a1dea59e0204c0931b5db808f5bd2e3b"><code>e44447c</code></a> fix(supabase): improve trace propagation sampling and diagnostics (<a href="https://github.com/supabase/supabase-js/tree/HEAD/packages/core/supabase-js/issues/2604">#2604</a>)</li> <li><a href="https://github.com/supabase/supabase-js/commit/9f0358ca7f2049868fe396fe4b0b5139577a3922"><code>9f0358c</code></a> fix(supabase): add trace context headers to canonical CORS allow-list (<a href="https://github.com/supabase/supabase-js/tree/HEAD/packages/core/supabase-js/issues/2603">#2603</a>)</li> <li><a href="https://github.com/supabase/supabase-js/commit/84beab1d1cff1e0930debfd00d3c154dcfe887a7"><code>84beab1</code></a> chore(release): version 2.112.2 changelogs (<a href="https://github.com/supabase/supabase-js/tree/HEAD/packages/core/supabase-js/issues/2599">#2599</a>)</li> <li>See full diff in <a href="https://github.com/supabase/supabase-js/commits/v2.112.3/packages/core/supabase-js">compare view</a></li> </ul> </details> <br /> Updates `@anthropic-ai/claude-agent-sdk` from 0.3.227 to 0.3.228 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/anthropics/claude-agent-sdk-typescript/releases">@anthropic-ai/claude-agent-sdk's releases</a>.</em></p> <blockquote> <h2>v0.3.228</h2> <h2>What's changed</h2> <ul> <li>Agent tool results (<code>AgentOutput</code>): <code>usage.output_tokens_details</code> is now carried through</li> </ul> <h2>Update</h2> <pre lang="sh"><code>npm install @anthropic-ai/claude-agent-sdk@0.3.228 # or yarn add @anthropic-ai/claude-agent-sdk@0.3.228 # or pnpm add @anthropic-ai/claude-agent-sdk@0.3.228 # or bun add @anthropic-ai/claude-agent-sdk@0.3.228 </code></pre> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/anthropics/claude-agent-sdk-typescript/blob/main/CHANGELOG.md">@anthropic-ai/claude-agent-sdk's changelog</a>.</em></p> <blockquote> <h2>0.3.228</h2> <ul> <li>Agent tool results (<code>AgentOutput</code>): <code>usage.output_tokens_details</code> is now carried through</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/anthropics/claude-agent-sdk-typescript/commit/0a2639d6b561af90342d4a98c93f9cc807d0e5ce"><code>0a2639d</code></a> chore: Update CHANGELOG.md</li> <li>See full diff in <a href="https://github.com/anthropics/claude-agent-sdk-typescript/compare/v0.3.227...v0.3.228">compare view</a></li> </ul> </details> <br /> Updates `@vercel/detect-agent` from 1.2.4 to 1.2.5 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vercel/vercel/releases">@vercel/detect-agent's releases</a>.</em></p> <blockquote> <h2><code>@vercel/h3</code><a href="https://github.com/0"><code>@0</code></a>.1.116</h2> <h3>Patch Changes</h3> <ul> <li><code>@vercel/node</code><a href="https://github.com/5"><code>@5</code></a>.9.3</li> </ul> <h2><code>@vercel/h3</code><a href="https://github.com/0"><code>@0</code></a>.1.115</h2> <h3>Patch Changes</h3> <ul> <li><code>@vercel/node</code><a href="https://github.com/5"><code>@5</code></a>.9.2</li> </ul> <h2><code>@vercel/h3</code><a href="https://github.com/0"><code>@0</code></a>.1.114</h2> <h3>Patch Changes</h3> <ul> <li><code>@vercel/node</code><a href="https://github.com/5"><code>@5</code></a>.9.1</li> </ul> <h2><code>@vercel/h3</code><a href="https://github.com/0"><code>@0</code></a>.1.113</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies [4502520] <ul> <li><code>@vercel/node</code><a href="https://github.com/5"><code>@5</code></a>.9.0</li> </ul> </li> </ul> <h2><code>@vercel/h3</code><a href="https://github.com/0"><code>@0</code></a>.1.112</h2> <h3>Patch Changes</h3> <ul> <li><code>@vercel/node</code><a href="https://github.com/5"><code>@5</code></a>.8.27</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/vercel/vercel/commits/@vercel/ruby@1.2.5/packages/detect-agent">compare view</a></li> </ul> </details> <br /> Updates `knip` from 6.32.1 to 6.32.2 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/webpro-nl/knip/releases">knip's releases</a>.</em></p> <blockquote> <h2>Release 6.32.2</h2> <ul> <li>Support <code>oxfmt.config.mts</code> (<a href="https://github.com/webpro-nl/knip/tree/HEAD/packages/knip/issues/1933">#1933</a>) (795900191dc75eec8d1e717b866bf57e1e2912cc) - thanks <a href="https://github.com/joealden"><code>@joealden</code></a>!</li> <li>Support <code>oxlint.config.mts</code> (<a href="https://github.com/webpro-nl/knip/tree/HEAD/packages/knip/issues/1934">#1934</a>) (531e2dc7c1d8bf31babea0068c34391182ec2d50) - thanks <a href="https://github.com/joealden"><code>@joealden</code></a>!</li> <li>Fix Supported <code>lint-staged</code> Configs (<a href="https://github.com/webpro-nl/knip/tree/HEAD/packages/knip/issues/1935">#1935</a>) (f9c755e414ed10baa4d01af8ddac6d04cb8d5617) - thanks <a href="https://github.com/joealden"><code>@joealden</code></a>!</li> <li>Update dependencies (95f7c529f918dd9e1a84f92c68d064738977b825)</li> <li>Update sentry snapshot (ea7929fcbd6b323c8bdd9252ac57017feeb29ecf)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/webpro-nl/knip/commit/196a11a4e0cb5208c0dc8382a54341d5630af631"><code>196a11a</code></a> Release knip@6.32.2</li> <li><a href="https://github.com/webpro-nl/knip/commit/95f7c529f918dd9e1a84f92c68d064738977b825"><code>95f7c52</code></a> Update dependencies</li> <li><a href="https://github.com/webpro-nl/knip/commit/f9c755e414ed10baa4d01af8ddac6d04cb8d5617"><code>f9c755e</code></a> Fix Supported <code>lint-staged</code> Configs (<a href="https://github.com/webpro-nl/knip/tree/HEAD/packages/knip/issues/1935">#1935</a>)</li> <li><a href="https://github.com/webpro-nl/knip/commit/531e2dc7c1d8bf31babea0068c34391182ec2d50"><code>531e2dc</code></a> Support <code>oxlint.config.mts</code> (<a href="https://github.com/webpro-nl/knip/tree/HEAD/packages/knip/issues/1934">#1934</a>)</li> <li><a href="https://github.com/webpro-nl/knip/commit/795900191dc75eec8d1e717b866bf57e1e2912cc"><code>7959001</code></a> Support <code>oxfmt.config.mts</code> (<a href="https://github.com/webpro-nl/knip/tree/HEAD/packages/knip/issues/1933">#1933</a>)</li> <li>See full diff in <a href="https://github.com/webpro-nl/knip/commits/knip@6.32.2/packages/knip">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>

## TL;DR fixes `supabase start` and `functions serve` dying with edge-runtime's "failed to determine entrypoint" on Docker daemons that cannot see the client's filesystem (remote tcp `DOCKER_HOST` contexts, podman machines) - which was broken by #5712 moving the bootstrap `index.ts` out of the `sh -c` argv onto a single file host bind mount to fix the `Windows ENAMETOOLONG` crash - and #5847 making native `start` reuse that serve core which left the bind sourcing a host path such daemons silently materialize as an empty directory at `/root/index.ts` so now the bundled template is streamed into the created container with `docker cp` before `docker start`, the same delivery Kong, Postgres, and Supavisor secret files already use since: - #6022 which fixes bring-up on non local daemons while the earlier `ENAMETOOLONG` fix stays intact since nothing returns to the `spawn argv` and the template no longer stages on host disk at all.... ## ref: - closes: #6254

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>

…on (CLI-2218) (#6276) Fixes [CLI-2218](https://linear.app/supabase/issue/CLI-2218/support-drop-index-concurrently-in-migrations). The v2.109.0 fix for pipeline-incompatible statements (#5671, design from #5156) classifies statements that cannot run inside a transaction block and runs them standalone outside the migration batch. Its pattern list covers `CREATE [UNIQUE] INDEX CONCURRENTLY`, `REINDEX … CONCURRENTLY`, `VACUUM`, `ALTER SYSTEM`, and `CLUSTER` — but not `DROP INDEX CONCURRENTLY`, which was missed. A migration containing one still gets batched into the implicit transaction and PostgreSQL rejects it: ``` ERROR: DROP INDEX CONCURRENTLY cannot run inside a transaction block (SQLSTATE 25001) ``` This adds the missing `DROP INDEX CONCURRENTLY` pattern to `legacyIsPipelineIncompatible` in the TS legacy shell, and mirrors it in the Go sidecar's `isPipelineIncompatible` (`pkg/migration/file.go`), which is still reachable through the remaining Go-delegated paths that apply migrations (`db remote commit`, `db branch`). Reported by an enterprise customer running `db push` on v2.111.0. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…bel (#6275) ## Summary Ready PRs targeting `develop` already get Test, preview CLI packages, and PR-title lint. Stacked PRs (base is another branch) never enter those workflows, and drafts skip the jobs. This adds a `run-ci` label that calls the same Test and preview suites as reusable workflows, including while the PR is still a draft. Ready `develop` PRs stay on the existing workflows so required check names are unchanged. - Add `run-ci` to start the suite; remove it to cancel in-progress opt-in runs. - Other labels do not start or cancel Test / preview. - Independent of `run-live-e2e-ci`. - After a stacked PR is retargeted onto `develop`, push or reopen so the native required checks populate. The `run-ci` repository label already exists. ## Linked issue N/A — maintainer CI workflow (exempt).

@ref

Bumps the actions-major group with 3 updates: [jdx/mise-action](https://github.com/jdx/mise-action), [github/codeql-action/init](https://github.com/github/codeql-action) and [github/codeql-action/analyze](https://github.com/github/codeql-action). Updates `jdx/mise-action` from 4.2.4 to 4.2.5 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jdx/mise-action/releases">jdx/mise-action's releases</a>.</em></p> <blockquote> <h2>v4.2.5: Resilient mise downloads with automatic retries</h2> <p>A small patch release that makes setup more resilient to transient network failures when downloading mise.</p> <h2>Fixed</h2> <h3>Retry mise downloads after transient failures (<a href="https://redirect.github.com/jdx/mise-action/pull/597">#597</a> by <a href="https://github.com/jdx"><code>@jdx</code></a>)</h3> <p>The download helpers previously made a single <code>curl</code> or <code>wget</code> attempt, so a transient GitHub release-asset HTTP or TLS failure would abort setup before mise or any user command could run (see <a href="https://redirect.github.com/jdx/mise-action/issues/596">#596</a>).</p> <p>Downloads now run through a retry wrapper that makes up to five attempts with a 2s pause between failures, logging a warning on each retry. This applies consistently to binary, checksum, signature, and version fetches. Checksum and minisign verification still run only after a successful download — never inside the retry loop — so integrity guarantees are unchanged.</p> <p><strong>Full Changelog</strong>: <a href="https://github.com/jdx/mise-action/compare/v4.2.4...v4.2.5">https://github.com/jdx/mise-action/compare/v4.2.4...v4.2.5</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/jdx/mise-action/blob/main/CHANGELOG.md">jdx/mise-action's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <hr /> <h2><a href="https://github.com/jdx/mise-action/compare/v4.2.4..v4.2.5">4.2.5</a> - 2026-08-12</h2> <h3>🐛 Bug Fixes</h3> <ul> <li>retry mise downloads after transient failures (<a href="https://redirect.github.com/jdx/mise-action/issues/597">#597</a>) by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/mise-action/pull/597">#597</a></li> </ul> <hr /> <h2><a href="https://github.com/jdx/mise-action/compare/v4.2.3..v4.2.4">4.2.4</a> - 2026-08-01</h2> <h3>🐛 Bug Fixes</h3> <ul> <li>locking support detection with force-colored output (<a href="https://redirect.github.com/jdx/mise-action/issues/580">#580</a>) by <a href="https://github.com/scop"><code>@scop</code></a> in <a href="https://redirect.github.com/jdx/mise-action/pull/580">#580</a></li> </ul> <hr /> <h2><a href="https://github.com/jdx/mise-action/compare/v4.2.2..v4.2.3">4.2.3</a> - 2026-07-24</h2> <h3>🐛 Bug Fixes</h3> <ul> <li>export mise path entries to subsequent steps (<a href="https://redirect.github.com/jdx/mise-action/issues/575">#575</a>) by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/mise-action/pull/575">#575</a></li> </ul> <hr /> <h2><a href="https://github.com/jdx/mise-action/compare/v4.2.1..v4.2.2">4.2.2</a> - 2026-07-24</h2> <h3>🐛 Bug Fixes</h3> <ul> <li><strong>(release-plz)</strong> exit when git-cliff produces no version bump (<a href="https://redirect.github.com/jdx/mise-action/issues/566">#566</a>) by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/mise-action/pull/566">#566</a></li> <li>ensure <code>tar</code> supports Zstd (<a href="https://redirect.github.com/jdx/mise-action/issues/569">#569</a>) by <a href="https://github.com/JackMyers001"><code>@JackMyers001</code></a> in <a href="https://redirect.github.com/jdx/mise-action/pull/569">#569</a></li> </ul> <h3>📚 Documentation</h3> <ul> <li>update default value of <code>cache_key_prefix</code> (<a href="https://redirect.github.com/jdx/mise-action/issues/570">#570</a>) by <a href="https://github.com/muzimuzhi"><code>@muzimuzhi</code></a> in <a href="https://redirect.github.com/jdx/mise-action/pull/570">#570</a></li> </ul> <h3>New Contributors</h3> <ul> <li><a href="https://github.com/muzimuzhi"><code>@muzimuzhi</code></a> made their first contribution in <a href="https://redirect.github.com/jdx/mise-action/pull/570">#570</a></li> <li><a href="https://github.com/JackMyers001"><code>@JackMyers001</code></a> made their first contribution in <a href="https://redirect.github.com/jdx/mise-action/pull/569">#569</a></li> </ul> <hr /> <h2><a href="https://github.com/jdx/mise-action/compare/v4.2.0..v4.2.1">4.2.1</a> - 2026-07-16</h2> <h3>🐛 Bug Fixes</h3> <ul> <li>verify mise downloads with signed checksums (<a href="https://redirect.github.com/jdx/mise-action/issues/548">#548</a>) by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/mise-action/pull/548">#548</a></li> <li>exclude PATH from environment export (<a href="https://redirect.github.com/jdx/mise-action/issues/556">#556</a>) by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/mise-action/pull/556">#556</a></li> </ul> <h3>🔍 Other Changes</h3>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jdx/mise-action/commit/3c2e0cf82a5b2e5249f0d3635a4d83d0ae861518"><code>3c2e0cf</code></a> chore: release v4.2.5 (<a href="https://redirect.github.com/jdx/mise-action/issues/598">#598</a>)</li> <li><a href="https://github.com/jdx/mise-action/commit/9dda3952d607125725deac9ec10a5f0e245d266b"><code>9dda395</code></a> fix: retry mise downloads after transient failures (<a href="https://redirect.github.com/jdx/mise-action/issues/597">#597</a>)</li> <li><a href="https://github.com/jdx/mise-action/commit/9d2b3112374f613543eb1ba717ada58f1b83bbec"><code>9d2b311</code></a> chore(deps): update github/codeql-action action to v4.37.6 (<a href="https://redirect.github.com/jdx/mise-action/issues/593">#593</a>)</li> <li><a href="https://github.com/jdx/mise-action/commit/4213fbba8c81548f6aa95cc448267135e0f9bf81"><code>4213fbb</code></a> chore(deps): update jdx/mise-action action to v4.2.4 (<a href="https://redirect.github.com/jdx/mise-action/issues/594">#594</a>)</li> <li><a href="https://github.com/jdx/mise-action/commit/672dbd2c977768efa8a09c7b5aa0c325334016ef"><code>672dbd2</code></a> chore(deps): update zizmorcore/zizmor-action action to v0.6.2 (<a href="https://redirect.github.com/jdx/mise-action/issues/595">#595</a>)</li> <li><a href="https://github.com/jdx/mise-action/commit/5159765e490c25a07dea3e55ecc7b1fb6e4fea9b"><code>5159765</code></a> chore(deps): lock file maintenance (<a href="https://redirect.github.com/jdx/mise-action/issues/592">#592</a>)</li> <li><a href="https://github.com/jdx/mise-action/commit/c75b4f602dfba4d05f0680ffec1baf3661e71d4b"><code>c75b4f6</code></a> chore(deps): update jdx/mise-action action to v4.2.3 (<a href="https://redirect.github.com/jdx/mise-action/issues/590">#590</a>)</li> <li><a href="https://github.com/jdx/mise-action/commit/367cc0ddcb2e776616f955e442cd84690567b517"><code>367cc0d</code></a> chore(deps): update github/codeql-action action to v4.37.3 (<a href="https://redirect.github.com/jdx/mise-action/issues/589">#589</a>)</li> <li><a href="https://github.com/jdx/mise-action/commit/90e6e66efae5a7de65c8847f5ffbe21be3cbd262"><code>90e6e66</code></a> chore(deps): update zizmorcore/zizmor-action action to v0.6.1 (<a href="https://redirect.github.com/jdx/mise-action/issues/591">#591</a>)</li> <li><a href="https://github.com/jdx/mise-action/commit/7350bb812e8b9fe7c2368e7ed3520590633f74c9"><code>7350bb8</code></a> chore(deps): lock file maintenance (<a href="https://redirect.github.com/jdx/mise-action/issues/588">#588</a>)</li> <li>See full diff in <a href="https://github.com/jdx/mise-action/compare/7e36c90d9ab29c415a2384db3006f3ec8a8cc654...3c2e0cf82a5b2e5249f0d3635a4d83d0ae861518">compare view</a></li> </ul> </details> <br /> Updates `github/codeql-action/init` from 4.37.6 to 4.37.7 <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.7</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> </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> <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> <li>In addition to the existing input format, the <code>config-file</code> input for the <code>codeql-action/init</code> step will soon support a new <code>[owner/]repo[@ref][:path]</code> format. All components except the repository name are optional. If omitted, <code>owner</code> defaults to the same owner as the repository the analysis is running for, <code>ref</code> to <code>main</code>, and <code>path</code> to <code>.github/codeql-action.yaml</code>. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. <a href="https://redirect.github.com/github/codeql-action/pull/3973">#3973</a></li> </ul> <h2>4.36.3 - 01 Jul 2026</h2> <p>No user facing changes.</p> <h2>4.36.2 - 04 Jun 2026</h2>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/github/codeql-action/commit/ff2f1c621b7f889edc0d3c761ac2e6a3f8cdb0dd"><code>ff2f1c6</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4093">#4093</a> from github/update-v4.37.7-be7a3dbb8</li> <li><a href="https://github.com/github/codeql-action/commit/951a133f96aa2114dd747e9e437305335d0bde16"><code>951a133</code></a> Update changelog for v4.37.7</li> <li><a href="https://github.com/github/codeql-action/commit/be7a3dbb8147b82cd6d27e0707105b36aa190fc1"><code>be7a3db</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4087">#4087</a> from github/dependabot/npm_and_yarn/npm-minor-0aa561...</li> <li><a href="https://github.com/github/codeql-action/commit/9310334b11405b305d9444edfa56cd86e2f1e4fe"><code>9310334</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4086">#4086</a> from github/mbg/thread-action-state-to-codeql</li> <li><a href="https://github.com/github/codeql-action/commit/b4d8a54218a8792de9af2f6f32e33af899ca5212"><code>b4d8a54</code></a> Rebuild</li> <li><a href="https://github.com/github/codeql-action/commit/ab5db2519c3344f2fa61c711fa2d6ad135829200"><code>ab5db25</code></a> Bump the npm-minor group across 1 directory with 8 updates</li> <li><a href="https://github.com/github/codeql-action/commit/38055a3c3cf3979323eaf70fc6c73a8690250bde"><code>38055a3</code></a> Drop <code>logger</code> from <code>databaseInitCluster</code> in interface</li> <li><a href="https://github.com/github/codeql-action/commit/1f87aed5e66849f0c43ae147377cc77f2d98ac99"><code>1f87aed</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4085">#4085</a> from github/update-bundle/codeql-bundle-v2.26.3</li> <li><a href="https://github.com/github/codeql-action/commit/dc1b98ad1c2f13ccf9fc33fb82f32fc76f944253"><code>dc1b98a</code></a> Make <code>logger</code> available to <code>getCodeQLForCmd</code></li> <li><a href="https://github.com/github/codeql-action/commit/6f0220ee37121218af472efbde25f06907a4da4f"><code>6f0220e</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4084">#4084</a> from github/navntoft/bump-undici</li> <li>Additional commits viewable in <a href="https://github.com/github/codeql-action/compare/5595ccaf912efad79be6eef63a5619ff05969be3...ff2f1c621b7f889edc0d3c761ac2e6a3f8cdb0dd">compare view</a></li> </ul> </details> <br /> Updates `github/codeql-action/analyze` from 4.37.6 to 4.37.7 <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.7</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> </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> <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> <li>In addition to the existing input format, the <code>config-file</code> input for the <code>codeql-action/init</code> step will soon support a new <code>[owner/]repo[@ref][:path]</code> format. All components except the repository name are optional. If omitted, <code>owner</code> defaults to the same owner as the repository the analysis is running for, <code>ref</code> to <code>main</code>, and <code>path</code> to <code>.github/codeql-action.yaml</code>. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. <a href="https://redirect.github.com/github/codeql-action/pull/3973">#3973</a></li> </ul> <h2>4.36.3 - 01 Jul 2026</h2> <p>No user facing changes.</p> <h2>4.36.2 - 04 Jun 2026</h2>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/github/codeql-action/commit/ff2f1c621b7f889edc0d3c761ac2e6a3f8cdb0dd"><code>ff2f1c6</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4093">#4093</a> from github/update-v4.37.7-be7a3dbb8</li> <li><a href="https://github.com/github/codeql-action/commit/951a133f96aa2114dd747e9e437305335d0bde16"><code>951a133</code></a> Update changelog for v4.37.7</li> <li><a href="https://github.com/github/codeql-action/commit/be7a3dbb8147b82cd6d27e0707105b36aa190fc1"><code>be7a3db</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4087">#4087</a> from github/dependabot/npm_and_yarn/npm-minor-0aa561...</li> <li><a href="https://github.com/github/codeql-action/commit/9310334b11405b305d9444edfa56cd86e2f1e4fe"><code>9310334</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4086">#4086</a> from github/mbg/thread-action-state-to-codeql</li> <li><a href="https://github.com/github/codeql-action/commit/b4d8a54218a8792de9af2f6f32e33af899ca5212"><code>b4d8a54</code></a> Rebuild</li> <li><a href="https://github.com/github/codeql-action/commit/ab5db2519c3344f2fa61c711fa2d6ad135829200"><code>ab5db25</code></a> Bump the npm-minor group across 1 directory with 8 updates</li> <li><a href="https://github.com/github/codeql-action/commit/38055a3c3cf3979323eaf70fc6c73a8690250bde"><code>38055a3</code></a> Drop <code>logger</code> from <code>databaseInitCluster</code> in interface</li> <li><a href="https://github.com/github/codeql-action/commit/1f87aed5e66849f0c43ae147377cc77f2d98ac99"><code>1f87aed</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4085">#4085</a> from github/update-bundle/codeql-bundle-v2.26.3</li> <li><a href="https://github.com/github/codeql-action/commit/dc1b98ad1c2f13ccf9fc33fb82f32fc76f944253"><code>dc1b98a</code></a> Make <code>logger</code> available to <code>getCodeQLForCmd</code></li> <li><a href="https://github.com/github/codeql-action/commit/6f0220ee37121218af472efbde25f06907a4da4f"><code>6f0220e</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4084">#4084</a> from github/navntoft/bump-undici</li> <li>Additional commits viewable in <a href="https://github.com/github/codeql-action/compare/5595ccaf912efad79be6eef63a5619ff05969be3...ff2f1c621b7f889edc0d3c761ac2e6a3f8cdb0dd">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>

## TL;DR fixes the flaky stack readiness tests by replacing the live clock readiness race with deterministic virtual time and an owned 503 health endpoint.... ## ref: - spotted on: [job 96378991208](https://github.com/supabase/cli/actions/runs/32353950826/job/96378991208) & [job 95913000393](https://github.com/supabase/cli/actions/runs/32200465815/job/95913000393)

…ructions (#6281) ## Summary Updates the repo agent instructions (`AGENTS.md` files and the delegation-surface doc) to reflect where the CLI actually stands after the Go→TS migration: - **`src/legacy/` is the source of truth.** The rewritten `apps/cli/AGENTS.md` replaces the "Go CLI Authority" framing with a "Source of Truth" section: the compatibility standard is the legacy shell's own established behavior (tests, `SIDE_EFFECTS.md`, shipped output), not comparison against Go. It also explicitly disallows new comments/docs/helper names framed as "Go parity", with old framing cleaned up opportunistically. - **`next/` is frozen and departing.** The shell-architecture section now documents that `next/` development moves to its own branch and the folder will leave this tree; no new features land there. Porting-era guidance built around it ("Reusing next/ implementations") is removed, and the dual-write file-location rule is noted as leaving with `next/`. - **Go is a residual delegation surface, not a reference.** "Phase 0: Go Binary Wrapper" becomes "The Go Delegation Surface": the surface only shrinks, never grows, and `apps/cli-go/` is authoritative solely for the still-proxied commands' flag definitions until they are removed. `docs/go-cli-porting-status.md` and `apps/cli-e2e/AGENTS.md` get matching one-line reframes. - **Still-live invariants are kept, de-Go'd.** The parity checklist becomes "Legacy Shell Invariants" and the telemetry section now treats `shared/telemetry/event-catalog.ts` as canonical in its own right; all operational rules (telemetry ensuring, stderr error shape, `--debug` log format, `-o` vs `--output-format`, CLI-1546 spinner rule) survive unchanged. - **`docs/go-cli-divergences.md` is declared a frozen historical record** — new flags/features are just new CLI behavior and no longer tracked as divergences. Docs-only change; no runtime behavior is affected. ## 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): …`). - [ ] Tests added or updated for the change. (Docs-only — not applicable.) - [x] `pnpm check:all` and `pnpm test` pass for the workspace(s) I touched. (No code touched; no markdown checks in CI.) 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

) ## Summary The Edge Runtime container was always created with `--ulimit nofile=65536:65536` — a raise inherited from the Go CLI so many concurrent Deno isolates can run (#5151). Sandboxed hosts cap the hard nofile limit lower (e.g. 20,000 in the Claude Code sandbox), their docker daemon shares that cap, and requesting more than the daemon can grant fails the container start outright. This adds `edgeRuntimeNofileUlimit(platformOs)` in `@supabase/stack` and uses it at both docker call sites (stack service defs for the next shell, and `shared/functions/serve.ts` for legacy `functions serve`/`start`): - On Linux, the requested value is clamped to the process's own hard limit, read via `process.report.getReport().userLimits.open_files` (the standard runtime API, implemented by both Bun and Node — verified under Bun in a Linux container with a constrained `--ulimit`). - The clamp only ever lowers the request, so the worst case on an exotic setup (client more constrained than a remote/rootful daemon) is a smaller fd budget, never a failed start. - When the clamp lowers the request, the CLI emits a warning naming the reduced limit ("Edge Runtime file descriptor limit lowered to N: …") so the smaller fd budget is visible instead of silent. It surfaces through `Output.warn` in `startEdgeRuntimeContainer`, covering both `functions serve` and legacy `start`; the stack `ServiceDef` builder is pure with no output channel and stays silent. - Off Linux the full 65536 raise is kept, since the daemon runs in a VM with its own limits. The Go-parity divergence is documented in `apps/cli/docs/go-cli-divergences.md`. Reviewer notes: the helper stays a plain sync leaf (no failure modes/retries/resources) per the repo's Effect-native carve-out — both call sites are sync `ServiceDef` builders — and takes `platformOs` as input to match how the stack threads `platform.os` instead of reading `process.platform` ambiently. It now returns `{ arg, limit, clampWarning? }` with the host hard limit injectable (defaulting to the real `process.report` probe), so the clamp decision and warning text carry deterministic unit coverage alongside the pure seams (`hardNofileLimitFromReport`, `clampNofileLimit`), including the 20,000-cap case. ## Linked issue Closes CLI-2220 (Linear) - [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] `pnpm check:all` and `pnpm test` pass for the workspace(s) I touched. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

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>

## TL;DR Keep `supabase start` health probes to the local Kong gateway off HTTP(S) proxies restoring the previous Go CLI behavior for the CLI's canonical loopback addresses. ## What regressed? The native TypeScript port moved these probes from Go's `net/http` client to Bun's `fetch`. Go bypassed proxies for localhost and loopback addresses, while Bun honors `HTTP_PROXY` and `HTTPS_PROXY` unless `NO_PROXY` is configured... With a proxy configured, PostgREST and Edge Runtime readiness probes can be sent to the proxy instead of `127.0.0.1`, causing a healthy local stack to fail startup and roll back... ## fixed now by: Append `localhost`, `127.0.0.1`, and `[::1]` to Bun's active `NO_PROXY` variable immediately before `start` performs its local gateway probes. Existing exclusions are preserved, and the late placement keeps the synthetic value out of project dotenv resolution and container environments... ## Ref resolves: #3265 (comment)

…o/pkg in the go-minor group across 1 directory (#6285) Bumps the go-minor group with 1 update in the /apps/cli-go/pkg directory: [golang.org/x/mod](https://github.com/golang/mod). Updates `golang.org/x/mod` from 0.39.0 to 0.40.0 <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/golang/mod/commit/d3398d06de5fa5c71083d3d1c26f2cda73508e0f"><code>d3398d0</code></a> go.mod: update golang.org/x dependencies</li> <li><a href="https://github.com/golang/mod/commit/57549bfb0d25b5ff7eb4763aa1f029d7e5383232"><code>57549bf</code></a> sumdb: ignore unrelated hashes in Lookup</li> <li><a href="https://github.com/golang/mod/commit/96f62ae6e9cb1b123de383fa2542812c9ba3b7db"><code>96f62ae</code></a> sumdb/tlog: fix TileHashReader authentication bypass</li> <li>See full diff in <a href="https://github.com/golang/mod/compare/v0.39.0...v0.40.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=golang.org/x/mod&package-manager=go_modules&previous-version=0.39.0&new-version=0.40.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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>

## Summary - consolidate the monorepo on the cataloged TypeScript 7 package and replace native compiler inference with tsc - update the full Effect dependency family and cooldown exclusions to RC.111 without a shared-platform override - preserve CLI flag and legacy output behavior under RC.111, then refresh generated API and schema outputs ## Context This removes the parallel TypeScript aliases and stale Effect beta/RC pins. Effect RC.111 also makes boolean defaults and response decoding stricter, so the affected CLI boundaries now state their existing behavior explicitly.

…#6291) Bumps the npm-major group with 6 updates in the / directory: | Package | From | To | | --- | --- | --- | | [@anthropic-ai/claude-agent-sdk](https://github.com/anthropics/claude-agent-sdk-typescript) | `0.3.229` | `0.3.232` | | [@anthropic-ai/sdk](https://github.com/anthropics/anthropic-sdk-typescript) | `0.116.0` | `0.117.1` | | [posthog-node](https://github.com/PostHog/posthog-js/tree/HEAD/packages/node) | `5.48.2` | `5.49.0` | | [fumadocs-core](https://github.com/fuma-nama/fumadocs) | `16.14.3` | `16.14.4` | | [fumadocs-ui](https://github.com/fuma-nama/fumadocs) | `16.14.3` | `16.14.4` | | [next](https://github.com/vercel/next.js) | `16.3.0` | `16.3.1` | Updates `@anthropic-ai/claude-agent-sdk` from 0.3.229 to 0.3.232 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/anthropics/claude-agent-sdk-typescript/releases">@anthropic-ai/claude-agent-sdk's releases</a>.</em></p> <blockquote> <h2>v0.3.232</h2> <h2>What's changed</h2> <ul> <li>Subagent MCP <code>tool_result</code> frames whose result carries <code>_meta</code> now emit <code>tool_use_result</code> as <code>{ content, _meta }</code> (matching main-loop frames) instead of a bare value</li> <li><code>/context</code> result messages now carry a structured <code>context_usage</code> payload (new <code>SDKContextUsage</code> type), so consumers can render the context-usage card without parsing the markdown table</li> <li><code>vcs_state_changed</code> events now populate the <code>branch</code> field for push operations, sourced from the pushed ref</li> </ul> <h2>Update</h2> <pre lang="sh"><code>npm install @anthropic-ai/claude-agent-sdk@0.3.232 # or yarn add @anthropic-ai/claude-agent-sdk@0.3.232 # or pnpm add @anthropic-ai/claude-agent-sdk@0.3.232 # or bun add @anthropic-ai/claude-agent-sdk@0.3.232 </code></pre> <h2>v0.3.231</h2> <h2>What's changed</h2> <ul> <li>Updated to parity with Claude Code v2.1.231</li> </ul> <h2>Update</h2> <pre lang="sh"><code>npm install @anthropic-ai/claude-agent-sdk@0.3.231 # or yarn add @anthropic-ai/claude-agent-sdk@0.3.231 # or pnpm add @anthropic-ai/claude-agent-sdk@0.3.231 # or bun add @anthropic-ai/claude-agent-sdk@0.3.231 </code></pre> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/anthropics/claude-agent-sdk-typescript/blob/main/CHANGELOG.md">@anthropic-ai/claude-agent-sdk's changelog</a>.</em></p> <blockquote> <h2>0.3.232</h2> <ul> <li>Subagent MCP <code>tool_result</code> frames whose result carries <code>_meta</code> now emit <code>tool_use_result</code> as <code>{ content, _meta }</code> (matching main-loop frames) instead of a bare value</li> <li><code>/context</code> result messages now carry a structured <code>context_usage</code> payload (new <code>SDKContextUsage</code> type), so consumers can render the context-usage card without parsing the markdown table</li> <li><code>vcs_state_changed</code> events now populate the <code>branch</code> field for push operations, sourced from the pushed ref</li> </ul> <h2>0.3.231</h2> <ul> <li>Updated to parity with Claude Code v2.1.231</li> </ul> <h2>0.3.230</h2> <ul> <li>Updated to parity with Claude Code v2.1.230</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/anthropics/claude-agent-sdk-typescript/commit/8716a39f83dd7506e6421199caface603d4941ab"><code>8716a39</code></a> chore: Update CHANGELOG.md</li> <li><a href="https://github.com/anthropics/claude-agent-sdk-typescript/commit/b5321a4b65ec1b034fea19f684e2d8db728875da"><code>b5321a4</code></a> chore: Update CHANGELOG.md</li> <li>See full diff in <a href="https://github.com/anthropics/claude-agent-sdk-typescript/compare/v0.3.229...v0.3.232">compare view</a></li> </ul> </details> <br /> Updates `@anthropic-ai/sdk` from 0.116.0 to 0.117.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/anthropics/anthropic-sdk-typescript/releases">@anthropic-ai/sdk's releases</a>.</em></p> <blockquote> <h2>sdk: v0.117.1</h2> <h2>0.117.1 (2026-08-13)</h2> <p>Full Changelog: <a href="https://github.com/anthropics/anthropic-sdk-typescript/compare/sdk-v0.117.0...sdk-v0.117.1">sdk-v0.117.0...sdk-v0.117.1</a></p> <h3>Chores</h3> <ul> <li><strong>ci:</strong> allow manually re-publishing a package to npm from the release workflow (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/af60c1f980557368fb10c3701d8dc8a1fa75d70e">af60c1f</a>)</li> <li><strong>internal:</strong> tag uploaded preview builds with the branch name (<a href="https://redirect.github.com/anthropics/anthropic-sdk-typescript/issues/295">#295</a>) (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/228f44ee4848e6a26be27d26093635e2dba783ea">228f44e</a>)</li> </ul> <h2>sdk: v0.117.0</h2> <h2>0.117.0 (2026-08-13)</h2> <p>Full Changelog: <a href="https://github.com/anthropics/anthropic-sdk-typescript/compare/sdk-v0.116.0...sdk-v0.117.0">sdk-v0.116.0...sdk-v0.117.0</a></p> <h3>Features</h3> <ul> <li><strong>api:</strong> add output_behavior to dream creation (create a new memory store or update the input store in place) (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/6a5bd0f34d214759f97d485e46b09203fff3ea99">6a5bd0f</a>)</li> </ul> <h3>Bug Fixes</h3> <ul> <li><strong>build:</strong> include dotfiles when flattening dist during git installs (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/917dbbb40070dbd1f861b16fcf297720d96f691b">917dbbb</a>)</li> <li><strong>client:</strong> add models (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/a7bfbb1b31e9d1dffe9a83b90ec1d0dabf5c36db">a7bfbb1</a>)</li> <li><strong>messages:</strong> honor per-request timeout in the non-streaming long-request check (<a href="https://redirect.github.com/anthropics/anthropic-sdk-typescript/issues/272">#272</a>) (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/0fdd8a8feb5d16fbb943490a2b1e8ecf915596d6">0fdd8a8</a>)</li> <li><strong>streaming:</strong> apply all message_delta fields when accumulating streamed messages (<a href="https://redirect.github.com/anthropics/anthropic-sdk-typescript/issues/289">#289</a>) (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/7b82659d70201ae3edab846f1693366db7e62ce3">7b82659</a>)</li> <li><strong>tool-runner:</strong> forward the response container id to the next request (<a href="https://redirect.github.com/anthropics/anthropic-sdk-typescript/issues/271">#271</a>) (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/5bdee4a8ddd83e2f1c71daa429345b3b0fea4602">5bdee4a</a>)</li> <li><strong>tools:</strong> align path resolution, skill-archive members, and heartbeat bounds with the other SDKs (<a href="https://redirect.github.com/anthropics/anthropic-sdk-typescript/issues/264">#264</a>) (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/5fbc729c82ec3967c9f76428d0f733b5fa61ddd5">5fbc729</a>)</li> </ul> <h3>Chores</h3> <ul> <li><strong>ci:</strong> run breaking-change detection as a ci.yml job on every push (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/c34c1d53f3227b3978621590e67f5a33f5cad107">c34c1d5</a>)</li> <li><strong>internal:</strong> switch from yarn to pnpm (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/f4eeea09648620d35517513814ffdc3bd3080801">f4eeea0</a>)</li> <li><strong>tools:</strong> escape backslashes in skill archive exclusion patterns (<a href="https://redirect.github.com/anthropics/anthropic-sdk-typescript/issues/311">#311</a>) (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/67ede1c665883b7785af3240c749601d7ca19255">67ede1c</a>)</li> </ul> <h3>Documentation</h3> <ul> <li><strong>api:</strong> clarify that user profile name is optional for resold profiles (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/1b6fed5868bd16dd92120440d373da22084be237">1b6fed5</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/anthropics/anthropic-sdk-typescript/blob/main/CHANGELOG.md">@anthropic-ai/sdk's changelog</a>.</em></p> <blockquote> <h2>0.117.1 (2026-08-13)</h2> <p>Full Changelog: <a href="https://github.com/anthropics/anthropic-sdk-typescript/compare/sdk-v0.117.0...sdk-v0.117.1">sdk-v0.117.0...sdk-v0.117.1</a></p> <h3>Chores</h3> <ul> <li><strong>ci:</strong> allow manually re-publishing a package to npm from the release workflow (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/af60c1f980557368fb10c3701d8dc8a1fa75d70e">af60c1f</a>)</li> <li><strong>internal:</strong> tag uploaded preview builds with the branch name (<a href="https://redirect.github.com/anthropics/anthropic-sdk-typescript/issues/295">#295</a>) (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/228f44ee4848e6a26be27d26093635e2dba783ea">228f44e</a>)</li> </ul> <h2>0.117.0 (2026-08-13)</h2> <p>Full Changelog: <a href="https://github.com/anthropics/anthropic-sdk-typescript/compare/sdk-v0.116.0...sdk-v0.117.0">sdk-v0.116.0...sdk-v0.117.0</a></p> <h3>Features</h3> <ul> <li><strong>api:</strong> add output_behavior to dream creation (create a new memory store or update the input store in place) (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/6a5bd0f34d214759f97d485e46b09203fff3ea99">6a5bd0f</a>)</li> </ul> <h3>Bug Fixes</h3> <ul> <li><strong>build:</strong> include dotfiles when flattening dist during git installs (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/917dbbb40070dbd1f861b16fcf297720d96f691b">917dbbb</a>)</li> <li><strong>client:</strong> add models (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/a7bfbb1b31e9d1dffe9a83b90ec1d0dabf5c36db">a7bfbb1</a>)</li> <li><strong>messages:</strong> honor per-request timeout in the non-streaming long-request check (<a href="https://redirect.github.com/anthropics/anthropic-sdk-typescript/issues/272">#272</a>) (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/0fdd8a8feb5d16fbb943490a2b1e8ecf915596d6">0fdd8a8</a>)</li> <li><strong>streaming:</strong> apply all message_delta fields when accumulating streamed messages (<a href="https://redirect.github.com/anthropics/anthropic-sdk-typescript/issues/289">#289</a>) (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/7b82659d70201ae3edab846f1693366db7e62ce3">7b82659</a>)</li> <li><strong>tool-runner:</strong> forward the response container id to the next request (<a href="https://redirect.github.com/anthropics/anthropic-sdk-typescript/issues/271">#271</a>) (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/5bdee4a8ddd83e2f1c71daa429345b3b0fea4602">5bdee4a</a>)</li> <li><strong>tools:</strong> align path resolution, skill-archive members, and heartbeat bounds with the other SDKs (<a href="https://redirect.github.com/anthropics/anthropic-sdk-typescript/issues/264">#264</a>) (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/5fbc729c82ec3967c9f76428d0f733b5fa61ddd5">5fbc729</a>)</li> </ul> <h3>Chores</h3> <ul> <li><strong>ci:</strong> run breaking-change detection as a ci.yml job on every push (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/c34c1d53f3227b3978621590e67f5a33f5cad107">c34c1d5</a>)</li> <li><strong>internal:</strong> switch from yarn to pnpm (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/f4eeea09648620d35517513814ffdc3bd3080801">f4eeea0</a>)</li> <li><strong>tools:</strong> escape backslashes in skill archive exclusion patterns (<a href="https://redirect.github.com/anthropics/anthropic-sdk-typescript/issues/311">#311</a>) (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/67ede1c665883b7785af3240c749601d7ca19255">67ede1c</a>)</li> </ul> <h3>Documentation</h3> <ul> <li><strong>api:</strong> clarify that user profile name is optional for resold profiles (<a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/1b6fed5868bd16dd92120440d373da22084be237">1b6fed5</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/64a1e8e285bbcc4cef2b15ebcadccd8e5f6987ff"><code>64a1e8e</code></a> chore: release main</li> <li><a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/0281a291359489284c116d1adea6d13aa7a94b6d"><code>0281a29</code></a> chore(ci): allow manually re-publishing a package to npm from the release wor...</li> <li><a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/f3e060b568a09556fea9288b688e1191f28f0935"><code>f3e060b</code></a> chore(internal): tag uploaded preview builds with the branch name (<a href="https://redirect.github.com/anthropics/anthropic-sdk-typescript/issues/295">#295</a>)</li> <li><a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/6fcfb2c3fce958e59750df3e4a8fda969c5ff171"><code>6fcfb2c</code></a> chore: release main</li> <li><a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/1a1af331442d9e9fc4ba172d87e4bc46a48255b1"><code>1a1af33</code></a> codegen metadata</li> <li><a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/d6b8f40ffe75a80a53b1464b8cce05b54ecac40d"><code>d6b8f40</code></a> chore: release main</li> <li><a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/5edda861559d809092bead9617a1073324a64585"><code>5edda86</code></a> chore(tools): escape backslashes in skill archive exclusion patterns (<a href="https://redirect.github.com/anthropics/anthropic-sdk-typescript/issues/311">#311</a>)</li> <li><a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/07cf28ce9d07da7d7c2b96d064d7a370d261c5bc"><code>07cf28c</code></a> chore(internal): switch from yarn to pnpm</li> <li><a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/a751543f5e0ba2096cc49821c351f8b3a82216ab"><code>a751543</code></a> docs(api): clarify that user profile name is optional for resold profiles</li> <li><a href="https://github.com/anthropics/anthropic-sdk-typescript/commit/0c74ed0372883d85378e5f85526d072e12d1997b"><code>0c74ed0</code></a> fix(build): include dotfiles when flattening dist during git installs</li> <li>Additional commits viewable in <a href="https://github.com/anthropics/anthropic-sdk-typescript/compare/sdk-v0.116.0...sdk-v0.117.1">compare view</a></li> </ul> </details> <br /> Updates `posthog-node` from 5.48.2 to 5.49.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/PostHog/posthog-js/releases">posthog-node's releases</a>.</em></p> <blockquote> <h2>posthog-node@5.49.0</h2> <h2>5.49.0</h2> <h3>Minor Changes</h3> <ul> <li><a href="https://redirect.github.com/PostHog/posthog-js/pull/4289">#4289</a> <a href="https://github.com/PostHog/posthog-js/commit/c9086de42e1c7f102b6cca318c875bdf030d630f"><code>c9086de</code></a> Thanks <a href="https://github.com/carlos-marchal-ph"><code>@carlos-marchal-ph</code></a>! - Public beta <code>captureAi()</code> / <code>captureAiImmediate()</code>: AI events on a dedicated isolated endpoint with the event UUID returned. New <code>enableFullAiCapture</code> option replaces the internal <code>_useAiLane</code> / <code>_enableMultimodalCapture</code>; wrappers route through the AI endpoint and skip redaction/truncation when set (privacy mode still wins). (2026-08-13)</li> </ul> <h3>Patch Changes</h3> <ul> <li>Updated dependencies [<a href="https://github.com/PostHog/posthog-js/commit/c9086de42e1c7f102b6cca318c875bdf030d630f"><code>c9086de</code></a>]: <ul> <li><code>@posthog/core</code><a href="https://github.com/1"><code>@1</code></a>.48.0</li> </ul> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/PostHog/posthog-js/blob/main/packages/node/CHANGELOG.md">posthog-node's changelog</a>.</em></p> <blockquote> <h2>5.49.0</h2> <h3>Minor Changes</h3> <ul> <li><a href="https://redirect.github.com/PostHog/posthog-js/pull/4289">#4289</a> <a href="https://github.com/PostHog/posthog-js/commit/c9086de42e1c7f102b6cca318c875bdf030d630f"><code>c9086de</code></a> Thanks <a href="https://github.com/carlos-marchal-ph"><code>@carlos-marchal-ph</code></a>! - Public beta <code>captureAi()</code> / <code>captureAiImmediate()</code>: AI events on a dedicated isolated endpoint with the event UUID returned. New <code>enableFullAiCapture</code> option replaces the internal <code>_useAiLane</code> / <code>_enableMultimodalCapture</code>; wrappers route through the AI endpoint and skip redaction/truncation when set (privacy mode still wins). (2026-08-13)</li> </ul> <h3>Patch Changes</h3> <ul> <li>Updated dependencies [<a href="https://github.com/PostHog/posthog-js/commit/c9086de42e1c7f102b6cca318c875bdf030d630f"><code>c9086de</code></a>]: <ul> <li><code>@posthog/core</code><a href="https://github.com/1"><code>@1</code></a>.48.0</li> </ul> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/PostHog/posthog-js/commit/5c5d26c5b35c6d402e5aeffadc78b9e49d6690a8"><code>5c5d26c</code></a> chore: update versions and lockfile [version bump]</li> <li><a href="https://github.com/PostHog/posthog-js/commit/c9086de42e1c7f102b6cca318c875bdf030d630f"><code>c9086de</code></a> feat(aio): public beta captureAi with dedicated AI capture lane (<a href="https://github.com/PostHog/posthog-js/tree/HEAD/packages/node/issues/4289">#4289</a>)</li> <li>See full diff in <a href="https://github.com/PostHog/posthog-js/commits/posthog-node@5.49.0/packages/node">compare view</a></li> </ul> </details> <br /> Updates `fumadocs-core` from 16.14.3 to 16.14.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/fuma-nama/fumadocs/releases">fumadocs-core's releases</a>.</em></p> <blockquote> <h2>fumadocs@16.14.4</h2> <ul> <li><code>@fumadocs/base-ui</code><a href="https://github.com/16"><code>@16</code></a>.14.4</li> <li>fumadocs-core@16.14.4</li> <li>fumadocs-ui@16.14.4</li> </ul> <h3>Introduce <code>@fumari/image-size</code>, replacing <code>image-size</code> in <code>remarkImage</code></h3> <p>A fork of <a href="https://github.com/nodeca/probe-image-size">probe-image-size</a> with no dependencies of its own.</p> <pre lang="ts"><code>import { probe, imageSize } from '@fumari/image-size'; <p>await probe('./public/banner.png'); // { width: 1200, height: 630, type: 'png', mime: 'image/png' }<br /> await probe('<a href="https://example.com/banner.png">https://example.com/banner.png</a>', { timeout: 5000 });</p> <p>imageSize(bytes); // the same result, or <code>null</code><br /> </code></pre></p> <p><code>remarkImage</code> now uses it in both <code>fumadocs-core</code> and <code>@fumadocs/satteri</code>. Remote images are no longer downloaded in full just to be measured, and redirects are followed. Sizes are always in pixels, so an SVG sized in <code>em</code> or <code>pt</code> is converted instead of being skipped. Remote requests also time out after 30 seconds by default.</p> <p>One behaviour difference worth knowing: the supported formats are avif/heic/heif, bmp, gif, ico, jpeg, png, psd, svg, tiff and webp. Sizes for jxl, tga, pnm, dds, icns, cur, ktx and jp2 can no longer be resolved and go through <code>onError</code> instead.</p> <p>Sequential scanning stops after 512 KB, but that never loses an image: the one format that stores its dimensions past that point — TIFF with a trailing IFD — is resolved by following the header's pointer with a targeted read, using an HTTP <code>Range</code> request for remote files (and skipping through the body when the server ignores ranges).</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/fuma-nama/fumadocs/commit/29c344d6074b325134d724914af93f6f77a9bb5c"><code>29c344d</code></a> Version Packages (<a href="https://redirect.github.com/fuma-nama/fumadocs/issues/3470">#3470</a>)</li> <li><a href="https://github.com/fuma-nama/fumadocs/commit/9a040224283915412bcf17a607d2b260509c389b"><code>9a04022</code></a> chore: bump deps</li> <li><a href="https://github.com/fuma-nama/fumadocs/commit/de917ac1c70666e77b98eba1152b1c9b4d56d722"><code>de917ac</code></a> perf(core): improve image size fetcher</li> <li><a href="https://github.com/fuma-nama/fumadocs/commit/1f92a8d03568418e9c6fc925c6249b9ac2a5fa06"><code>1f92a8d</code></a> fix(preview): stale usage</li> <li>See full diff in <a href="https://github.com/fuma-nama/fumadocs/compare/fumadocs@16.14.3...fumadocs@16.14.4">compare view</a></li> </ul> </details> <br /> Updates `fumadocs-ui` from 16.14.3 to 16.14.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/fuma-nama/fumadocs/releases">fumadocs-ui's releases</a>.</em></p> <blockquote> <h2>fumadocs@16.14.4</h2> <ul> <li><code>@fumadocs/base-ui</code><a href="https://github.com/16"><code>@16</code></a>.14.4</li> <li>fumadocs-core@16.14.4</li> <li>fumadocs-ui@16.14.4</li> </ul> <h3>Introduce <code>@fumari/image-size</code>, replacing <code>image-size</code> in <code>remarkImage</code></h3> <p>A fork of <a href="https://github.com/nodeca/probe-image-size">probe-image-size</a> with no dependencies of its own.</p> <pre lang="ts"><code>import { probe, imageSize } from '@fumari/image-size'; <p>await probe('./public/banner.png'); // { width: 1200, height: 630, type: 'png', mime: 'image/png' }<br /> await probe('<a href="https://example.com/banner.png">https://example.com/banner.png</a>', { timeout: 5000 });</p> <p>imageSize(bytes); // the same result, or <code>null</code><br /> </code></pre></p> <p><code>remarkImage</code> now uses it in both <code>fumadocs-core</code> and <code>@fumadocs/satteri</code>. Remote images are no longer downloaded in full just to be measured, and redirects are followed. Sizes are always in pixels, so an SVG sized in <code>em</code> or <code>pt</code> is converted instead of being skipped. Remote requests also time out after 30 seconds by default.</p> <p>One behaviour difference worth knowing: the supported formats are avif/heic/heif, bmp, gif, ico, jpeg, png, psd, svg, tiff and webp. Sizes for jxl, tga, pnm, dds, icns, cur, ktx and jp2 can no longer be resolved and go through <code>onError</code> instead.</p> <p>Sequential scanning stops after 512 KB, but that never loses an image: the one format that stores its dimensions past that point — TIFF with a trailing IFD — is resolved by following the header's pointer with a targeted read, using an HTTP <code>Range</code> request for remote files (and skipping through the body when the server ignores ranges).</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/fuma-nama/fumadocs/commit/29c344d6074b325134d724914af93f6f77a9bb5c"><code>29c344d</code></a> Version Packages (<a href="https://redirect.github.com/fuma-nama/fumadocs/issues/3470">#3470</a>)</li> <li><a href="https://github.com/fuma-nama/fumadocs/commit/9a040224283915412bcf17a607d2b260509c389b"><code>9a04022</code></a> chore: bump deps</li> <li><a href="https://github.com/fuma-nama/fumadocs/commit/de917ac1c70666e77b98eba1152b1c9b4d56d722"><code>de917ac</code></a> perf(core): improve image size fetcher</li> <li><a href="https://github.com/fuma-nama/fumadocs/commit/1f92a8d03568418e9c6fc925c6249b9ac2a5fa06"><code>1f92a8d</code></a> fix(preview): stale usage</li> <li>See full diff in <a href="https://github.com/fuma-nama/fumadocs/compare/fumadocs@16.14.3...fumadocs@16.14.4">compare view</a></li> </ul> </details> <br /> Updates `next` from 16.3.0 to 16.3.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vercel/next.js/releases">next's releases</a>.</em></p> <blockquote> <h2>v16.3.1</h2> <h2>What's Changed</h2> <ul> <li>[16.x] Turbopack: don't strip async-module runtime from shared runtime chunks by <a href="https://github.com/lukesandberg"><code>@lukesandberg</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/96653">vercel/next.js#96653</a></li> <li>[16.x] [turbopack] Add <code>turbopack_ecmascript</code> and <code>turbopack_wasm</code>'s embeded FS to <code>internal_assets_conditions</code> by <a href="https://github.com/lukesandberg"><code>@lukesandberg</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/96655">vercel/next.js#96655</a></li> <li>[16.x] [turbopack] Collapse nested promises in the analyzer by <a href="https://github.com/sampoder"><code>@sampoder</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/96675">vercel/next.js#96675</a></li> <li>[16.x] fix(next/image): preserve image response after optimization by <a href="https://github.com/styfle"><code>@styfle</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/96733">vercel/next.js#96733</a></li> <li>[16.3.x] Default deploy e2e tests to the repo next version by <a href="https://github.com/eps1lon"><code>@eps1lon</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/96900">vercel/next.js#96900</a></li> <li>[backport] Bump <code>@swc/helpers</code> by <a href="https://github.com/mischnic"><code>@mischnic</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/96885">vercel/next.js#96885</a></li> <li>[backport] [turbopack] Raise registration calls in hoisted modules to the top by <a href="https://github.com/lukesandberg"><code>@lukesandberg</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/97308">vercel/next.js#97308</a></li> <li>[backport] Fix missing styled-jsx styles in Pages Router SSR on adapter builds by <a href="https://github.com/lukesandberg"><code>@lukesandberg</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/97302">vercel/next.js#97302</a></li> <li>[backport] [turbopack] Fix HMR for dynamic imports evaluated from layouts by <a href="https://github.com/lukesandberg"><code>@lukesandberg</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/97317">vercel/next.js#97317</a></li> <li>[backport] Restore the live <code>headers()</code> view of the incoming request by <a href="https://github.com/unstubbable"><code>@unstubbable</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/97311">vercel/next.js#97311</a></li> <li>[backport] Allow literal exports in <code>'use cache'</code> files by <a href="https://github.com/unstubbable"><code>@unstubbable</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/97312">vercel/next.js#97312</a></li> <li>[backport] Keep the dev validation worker alive across HMR updates by <a href="https://github.com/unstubbable"><code>@unstubbable</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/97315">vercel/next.js#97315</a></li> <li>[backport] Discard only cache entries that predate a tag revalidation, and reuse completed entries by <a href="https://github.com/unstubbable"><code>@unstubbable</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/97314">vercel/next.js#97314</a></li> <li>[backport] Encode the cache item name built by <code>unstable_cache</code> by <a href="https://github.com/unstubbable"><code>@unstubbable</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/97313">vercel/next.js#97313</a></li> <li>[16.3] [ci] Use OIDC tokens to read private preview builds by <a href="https://github.com/eps1lon"><code>@eps1lon</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/97258">vercel/next.js#97258</a></li> <li>[backport] [test] Compile the middleware redirect routes up front in dev by <a href="https://github.com/lukesandberg"><code>@lukesandberg</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/97328">vercel/next.js#97328</a></li> <li>[backport] Fix Nav Inspector request loop on repeat captures by <a href="https://github.com/acdlite"><code>@acdlite</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/97326">vercel/next.js#97326</a></li> <li>[backport] Fix: Optimistic routing bugs leading to repeated prefetch loops by <a href="https://github.com/acdlite"><code>@acdlite</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/97325">vercel/next.js#97325</a></li> <li>[backport] Retain fewer stale cache versions and use a TTL, plus the mtime fallback by <a href="https://github.com/lukesandberg"><code>@lukesandberg</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/97304">vercel/next.js#97304</a></li> <li>[backport] Revert i18n localization change for dynamic Pages API routes (<a href="https://redirect.github.com/vercel/next.js/issues/94905">#94905</a>) by <a href="https://github.com/gaojude"><code>@gaojude</code></a> in <a href="https://redirect.github.com/vercel/next.js/pull/97330">vercel/next.js#97330</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/vercel/next.js/compare/v16.3.0...v16.3.1">https://github.com/vercel/next.js/compare/v16.3.0...v16.3.1</a></p> <h2>v16.3.1-canary.26</h2> <h3>Misc Changes</h3> <ul> <li>docs: document deploymentId build ID override and Pages Router skew in 16.2: <a href="https://redirect.github.com/vercel/next.js/issues/97645">#97645</a></li> <li>Upgrade React from <code>eb8feb71-20260814</code> to <code>eafeac09-20260819</code>: <a href="https://redirect.github.com/vercel/next.js/issues/97636">#97636</a></li> <li>Turbopack: rename to use turbopack: no side effects: <a href="https://redirect.github.com/vercel/next.js/issues/94427">#94427</a></li> <li>refactor: move useDynamic{Route,Search}Params to reduce snapshot churn: <a href="https://redirect.github.com/vercel/next.js/issues/97360">#97360</a></li> <li>[PPF] unstable_navigation(): <a href="https://redirect.github.com/vercel/next.js/issues/96908">#96908</a></li> <li>[PPF] Scaffold unstable_navigation(): <a href="https://redirect.github.com/vercel/next.js/issues/97236">#97236</a></li> <li>docs: Explicit cache output description: <a href="https://redirect.github.com/vercel/next.js/issues/97548">#97548</a></li> <li>Improve Cache Components sync IO migration guidance: <a href="https://redirect.github.com/vercel/next.js/issues/97572">#97572</a></li> <li>[test] Use a non-native stub for the server externals list test: <a href="https://redirect.github.com/vercel/next.js/issues/97614">#97614</a></li> <li>Avoid GitHub API rate limits for create-next-app examples: <a href="https://redirect.github.com/vercel/next.js/issues/97612">#97612</a></li> <li>[test] Cover the prerender worker-thread backend with an addon we control: <a href="https://redirect.github.com/vercel/next.js/issues/97543">#97543</a></li> <li>[test] Convert the <code>prerender-native-module</code> suite to local fixture packages: <a href="https://redirect.github.com/vercel/next.js/issues/97542">#97542</a></li> <li>[test] Replace the <code>turbopack-reports</code> <code>sqlite3</code> dependency with a local addon fixture: <a href="https://redirect.github.com/vercel/next.js/issues/97541">#97541</a></li> <li>[test] Drop the dead <code>sqlite3</code> build approval from the <code>sharp-basic</code> suite: <a href="https://redirect.github.com/vercel/next.js/issues/97540">#97540</a></li> <li>[ci] Authenticate Turborepo remote caching with OIDC instead of a static PAT: <a href="https://redirect.github.com/vercel/next.js/issues/97590">#97590</a></li> <li>Remove HmrTarget: <a href="https://redirect.github.com/vercel/next.js/issues/97253">#97253</a></li> <li>Keep HMR instructions typed until serialization: <a href="https://redirect.github.com/vercel/next.js/issues/96569">#96569</a></li> <li>Serialize frozen collections by value only: <a href="https://redirect.github.com/vercel/next.js/issues/96686">#96686</a></li> </ul> <h3>Credits</h3>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vercel/next.js/commit/3d32eb870fb4c7009d580a31e2de81a626562270"><code>3d32eb8</code></a> v16.3.1</li> <li><a href="https://github.com/vercel/next.js/commit/2b4b1ec111e76c70a18a59a96ef9e05573d916a3"><code>2b4b1ec</code></a> [backport] Revert i18n localization change for dynamic Pages API routes (<a href="https://redirect.github.com/vercel/next.js/issues/949">#949</a>...</li> <li><a href="https://github.com/vercel/next.js/commit/228df5fd74810d5e38d63d08641972cdec53306c"><code>228df5f</code></a> [backport] Retain fewer stale cache versions and use a TTL, plus the mtime fa...</li> <li><a href="https://github.com/vercel/next.js/commit/16eab3ac5d41d2e13d772cafcba949dba354d4c0"><code>16eab3a</code></a> [backport] Fix: Optimistic routing bugs leading to repeated prefetch loops (#...</li> <li><a href="https://github.com/vercel/next.js/commit/75548c9a2bc9f7031ec74d3dbf9ea3c51a9f802d"><code>75548c9</code></a> [backport] Fix Nav Inspector request loop on repeat captures (<a href="https://redirect.github.com/vercel/next.js/issues/97326">#97326</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/f6bd714a79dda91b759a97761765639e564617fe"><code>f6bd714</code></a> [backport] [test] Compile the middleware redirect routes up front in dev (<a href="https://redirect.github.com/vercel/next.js/issues/97">#97</a>...</li> <li><a href="https://github.com/vercel/next.js/commit/43c1c60bca17164c201810ce35f791b8ffde083b"><code>43c1c60</code></a> [16.3] [ci] Use OIDC tokens to read private preview builds (<a href="https://redirect.github.com/vercel/next.js/issues/97258">#97258</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/9dbb357dbebffbf90a29a51eee7778b6c77abd68"><code>9dbb357</code></a> [backport] Encode the cache item name built by <code>unstable_cache</code> (<a href="https://redirect.github.com/vercel/next.js/issues/97313">#97313</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/323a17c1b3e12651b71ebd465cac02ab4e50aa30"><code>323a17c</code></a> [backport] Discard only cache entries that predate a tag revalidation, and re...</li> <li><a href="https://github.com/vercel/next.js/commit/6d67f46a4dd558191c539a475b8531ee8a5c16b4"><code>6d67f46</code></a> [backport] Keep the dev validation worker alive across HMR updates (<a href="https://redirect.github.com/vercel/next.js/issues/97315">#97315</a>)</li> <li>Additional commits viewable in <a href="https://github.com/vercel/next.js/compare/v16.3.0...v16.3.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>

## Summary - update the local and CI Bun runtime pins to 1.4.0 - refresh the generated Mise lock data and Bun type definitions - keep Istanbul coverage in place until Bun’s V8 coverage fix ships in a later release ## Context Bun 1.4.0’s V8 coverage path currently fails against this suite because it emits invalid zero-length ranges. This update therefore leaves the existing Istanbul provider unchanged and limits the change to the runtime and tooling upgrade. ## Binary size comparison Uncompressed executable sizes from the [successful preview build](https://github.com/supabase/cli/actions/runs/32490402284/job/96800354277), compared with the current production [v2.115.0](https://github.com/supabase/cli/releases/tag/v2.115.0) platform packages: | Platform | Preview Bun 1.4 | Production | Difference | |---|---:|---:|---:| | macOS arm64 | 69.30 MiB | 68.45 MiB | +0.85 MiB (+1.24%) | | macOS x64 | 75.79 MiB | 73.44 MiB | +2.35 MiB (+3.20%) | | Linux arm64, glibc | 91.74 MiB | 109.69 MiB | −17.95 MiB (−16.37%) | | Linux arm64, musl | 85.07 MiB | 104.13 MiB | −19.06 MiB (−18.31%) | | Linux x64, glibc | 92.36 MiB | 109.85 MiB | −17.49 MiB (−15.92%) | | Linux x64, musl | 86.39 MiB | 104.94 MiB | −18.55 MiB (−17.68%) | | Windows arm64 | 84.28 MiB | 118.51 MiB | −34.23 MiB (−28.88%) | | Windows x64 | 94.30 MiB | 121.08 MiB | −26.78 MiB (−22.12%) | Bun 1.4 reduces the Linux and Windows binaries by roughly 16–29%, while the macOS binaries increase by 1–3%. --------- Co-authored-by: kanad <git@kanad.dev>

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> Co-authored-by: Julien Goux <hi@jgoux.dev>

…/apps/cli-go/pkg/config/templates (#6258) Bumps supabase/postgres from 17.6.1.159 to 17.6.1.165. [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=supabase/postgres&package-manager=docker&previous-version=17.6.1.159&new-version=17.6.1.165)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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 this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </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>

…emplates with 4 updates (#6257) Bumps the docker-minor group in /apps/cli-go/pkg/config/templates with 4 updates: supabase/gotrue, supabase/realtime, supabase/storage-api and supabase/logflare. Updates `supabase/gotrue` from v2.195.0 to v2.196.0 Updates `supabase/realtime` from v2.129.0 to v2.129.3 Updates `supabase/storage-api` from v1.69.11 to v1.70.3 Updates `supabase/logflare` from 1.50.2 to 1.50.4 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>

## Summary - make the `@supabase/stack` runtime core Effect-native across Node and Bun, with Promise adapters only at the public non-Effect edge - add package-owned `off`, `lazy`, and `eager` preparation policies with dependency closure, bounded concurrency, coalesced work, and deterministic disposal - resolve native slim-service releases through exact manifests and checksums, asynchronous in-process zstd decompression, host compatibility gates, typed post-processing, and atomic cache publication - select one exclusive native or Docker/Podman runtime, persist that concrete selection for managed stacks, and use it consistently for preparation, execution, logs, and cleanup - centralize managed identity, lifecycle documents, sticky port intent, control ownership, stale-owner recovery, and detached supervision in one manager and lifecycle facade - harden process-compose lifecycle transitions with Effect fibers, scopes, semaphores, typed failures, and interruption-safe resource cleanup ## Context Direct and managed stacks now share one service graph, preparation pipeline, port allocator, proxy, and process lifecycle. Direct callers own a scoped in-process handle. Managed callers use a detached supervisor with one durable document and one loopback control owner; CLI handlers delegate to that facade instead of maintaining PID-based liveness or parallel metadata. When mode is omitted, selection prefers a usable Docker or Podman runtime. If neither is usable on a supported host, the first launch selects native mode and disables Docker-only services before port planning or managed state acquisition. Explicit native and Docker choices remain strict, preparation never falls back across modes, and a managed stack pins its selected runtime after ownership is acquired. Changing modes requires deleting and recreating that private managed stack state. Preparation is driven by the service catalog. Eager resources are prepared during stack start, lazy resources use the same activation path as proxy and programmatic callers, and concurrent requests join the same owned work. Native archives are verified before extraction, decompressed through an interruptible callback boundary, validated for the current host, post-processed with checked exit codes, and published from private staging through atomic rename. Docker services resolve one canonical GHCR image and retry only classified transient pull failures. Port allocation owns bound sockets until each runtime consumer takes over. Explicit ports remain exact; automatic managed assignments remain sticky and are coordinated with per-user claims. Managed control uses a deterministic sequence of eight loopback candidates, read-only probes never claim ownership, and mutations fail closed when no unambiguous owner or free candidate exists. Native mode currently supports Postgres, Auth, and PostgREST. Docker-only services remain container-backed. On Linux, Docker Postgres performs only the required image setup as root and then drops to the host UID before touching bind-mounted data. Database bootstrap is a resumable observable one-shot dependency, and cleanup is scoped to exact owned containers, ports, processes, and auto-managed paths. The managed document and identity markers are private unreleased state. This change intentionally implements the current model directly without legacy migration or compatibility adapters, while preserving fail-loud ownership and destructive-cleanup safeguards.

…n /apps/cli-go in the go-minor group across 1 directory (#6297) Bumps the go-minor group with 1 update in the /apps/cli-go directory: [github.com/posthog/posthog-go](https://github.com/posthog/posthog-go). Updates `github.com/posthog/posthog-go` from 1.23.0 to 1.23.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/posthog/posthog-go/releases">github.com/posthog/posthog-go's releases</a>.</em></p> <blockquote> <h2>1.23.1</h2> <h2>Unreleased</h2> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/PostHog/posthog-go/blob/main/CHANGELOG.md">github.com/posthog/posthog-go's changelog</a>.</em></p> <blockquote> <h2>1.23.1</h2> <h3>Patch Changes</h3> <ul> <li>ec8f6c0: Normalize event timestamps to the equivalent UTC instant before serializing legacy batch and Capture V1 payloads.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/PostHog/posthog-go/commit/608be686da59a4388c5488c47013c88704b5a0eb"><code>608be68</code></a> chore: release v1.23.1 [version bump] [skip ci]</li> <li><a href="https://github.com/PostHog/posthog-go/commit/ec8f6c062d71056e6f0cd2b898dc15710e3d7671"><code>ec8f6c0</code></a> fix: normalize SDK timestamps to UTC (<a href="https://redirect.github.com/posthog/posthog-go/issues/284">#284</a>)</li> <li><a href="https://github.com/PostHog/posthog-go/commit/7fb10e66f9454d49c783f25115d23ef904ebab5d"><code>7fb10e6</code></a> ci: remove automerge from upgrade workflow (<a href="https://redirect.github.com/posthog/posthog-go/issues/282">#282</a>)</li> <li><a href="https://github.com/PostHog/posthog-go/commit/4127d7dd3d32198d5bea04f1df4463c8c90f2443"><code>4127d7d</code></a> ci: Upgrade posthog-go in the PostHog monorepo after releases (<a href="https://redirect.github.com/posthog/posthog-go/issues/281">#281</a>)</li> <li><a href="https://github.com/PostHog/posthog-go/commit/f7b86e8b2e08c6660c1f9a724e1b0a8dbcb088ca"><code>f7b86e8</code></a> chore(deps): bump the github-actions group with 3 updates (<a href="https://redirect.github.com/posthog/posthog-go/issues/280">#280</a>)</li> <li><a href="https://github.com/PostHog/posthog-go/commit/a02322f2f6717921adf56337b0389326e5854cde"><code>a02322f</code></a> chore: group Dependabot updates (<a href="https://redirect.github.com/posthog/posthog-go/issues/278">#278</a>)</li> <li><a href="https://github.com/PostHog/posthog-go/commit/e6df36629e92c6ce3d8455c5849c63e2b110bd41"><code>e6df366</code></a> chore(deps): bump github/codeql-action/analyze from 4.35.5 to 4.37.4 (<a href="https://redirect.github.com/posthog/posthog-go/issues/274">#274</a>)</li> <li><a href="https://github.com/PostHog/posthog-go/commit/3a67823f277c2a6c61b91d7147d5dcd211618323"><code>3a67823</code></a> chore(deps-dev): bump <code>@changesets/cli</code> from 2.31.0 to 2.31.1 (<a href="https://redirect.github.com/posthog/posthog-go/issues/269">#269</a>)</li> <li><a href="https://github.com/PostHog/posthog-go/commit/f2742c59513061583d4895e482b8e5b7d616c635"><code>f2742c5</code></a> chore(deps): bump github.com/goccy/go-json from 0.10.5 to 0.10.6 (<a href="https://redirect.github.com/posthog/posthog-go/issues/271">#271</a>)</li> <li><a href="https://github.com/PostHog/posthog-go/commit/5bb890ea42c33ddbdad33c451f35e3d2fb32eef7"><code>5bb890e</code></a> chore(deps): bump actions/checkout from 6.0.2 to 7.0.1 (<a href="https://redirect.github.com/posthog/posthog-go/issues/273">#273</a>)</li> <li>Additional commits viewable in <a href="https://github.com/posthog/posthog-go/compare/v1.23.0...v1.23.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github.com/posthog/posthog-go&package-manager=go_modules&previous-version=1.23.0&new-version=1.23.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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>

Bumps the npm-major group with 3 updates: [pkg-pr-new](https://github.com/stackblitz-labs/pkg.pr.new/tree/HEAD/packages/cli), [@anthropic-ai/claude-agent-sdk](https://github.com/anthropics/claude-agent-sdk-typescript) and [posthog-node](https://github.com/PostHog/posthog-js/tree/HEAD/packages/node). Updates `pkg-pr-new` from 0.0.87 to 0.0.88 <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/stackblitz-labs/pkg.pr.new/commit/b594954a191af6b4b318dd8a0511f22c7b6d1ec4"><code>b594954</code></a> release: v0.0.88</li> <li>See full diff in <a href="https://github.com/stackblitz-labs/pkg.pr.new/commits/v0.0.88/packages/cli">compare view</a></li> </ul> </details> <br /> Updates `@anthropic-ai/claude-agent-sdk` from 0.3.232 to 0.3.233 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/anthropics/claude-agent-sdk-typescript/releases">@anthropic-ai/claude-agent-sdk's releases</a>.</em></p> <blockquote> <h2>v0.3.233</h2> <h2>What's changed</h2> <ul> <li>Notification hooks now fire for pending permission prompts on the SDK path, matching the interactive REPL behavior</li> <li>Todo/task-tracking tools (<code>TaskCreate</code>/<code>TaskGet</code>/<code>TaskUpdate</code>/<code>TaskList</code>, <code>TodoWrite</code>) are no longer in the default tool surface on Opus 4.8, Sonnet 5, Fable 5, Mythos 5, and newer models; name them in the <code>tools</code> option or reference them in <code>allowedTools</code> (or set <code>CLAUDE_CODE_ENABLE_TODO_TOOLS=1</code>) to keep them</li> </ul> <h2>Update</h2> <pre lang="sh"><code>npm install @anthropic-ai/claude-agent-sdk@0.3.233 # or yarn add @anthropic-ai/claude-agent-sdk@0.3.233 # or pnpm add @anthropic-ai/claude-agent-sdk@0.3.233 # or bun add @anthropic-ai/claude-agent-sdk@0.3.233 </code></pre> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/anthropics/claude-agent-sdk-typescript/blob/main/CHANGELOG.md">@anthropic-ai/claude-agent-sdk's changelog</a>.</em></p> <blockquote> <h2>0.3.233</h2> <ul> <li>Notification hooks now fire for pending permission prompts on the SDK path, matching the interactive REPL behavior</li> <li>Todo/task-tracking tools (<code>TaskCreate</code>/<code>TaskGet</code>/<code>TaskUpdate</code>/<code>TaskList</code>, <code>TodoWrite</code>) are no longer in the default tool surface on Opus 4.8, Sonnet 5, Fable 5, Mythos 5, and newer models; name them in the <code>tools</code> option or reference them in <code>allowedTools</code> (or set <code>CLAUDE_CODE_ENABLE_TODO_TOOLS=1</code>) to keep them</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/anthropics/claude-agent-sdk-typescript/commit/73a28abad0d5015568404ecfe0d9cad3ed479fe3"><code>73a28ab</code></a> chore: Update CHANGELOG.md</li> <li>See full diff in <a href="https://github.com/anthropics/claude-agent-sdk-typescript/compare/v0.3.232...v0.3.233">compare view</a></li> </ul> </details> <br /> Updates `posthog-node` from 5.49.0 to 5.49.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/PostHog/posthog-js/releases">posthog-node's releases</a>.</em></p> <blockquote> <h2>posthog-node@5.49.1</h2> <h2>5.49.1</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/PostHog/posthog-js/pull/4521">#4521</a> <a href="https://github.com/PostHog/posthog-js/commit/0a0206f907f4b58dc28f36aa1fc441b55c489faf"><code>0a0206f</code></a> Thanks <a href="https://github.com/marandaneto"><code>@marandaneto</code></a>! - Normalize capture timestamp overrides to equivalent UTC ISO strings in the browser and Node.js SDKs and shared core. (2026-08-14)</li> <li>Updated dependencies [<a href="https://github.com/PostHog/posthog-js/commit/0a0206f907f4b58dc28f36aa1fc441b55c489faf"><code>0a0206f</code></a>]: <ul> <li><code>@posthog/core</code><a href="https://github.com/1"><code>@1</code></a>.48.1</li> </ul> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/PostHog/posthog-js/blob/main/packages/node/CHANGELOG.md">posthog-node's changelog</a>.</em></p> <blockquote> <h2>5.49.1</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/PostHog/posthog-js/pull/4521">#4521</a> <a href="https://github.com/PostHog/posthog-js/commit/0a0206f907f4b58dc28f36aa1fc441b55c489faf"><code>0a0206f</code></a> Thanks <a href="https://github.com/marandaneto"><code>@marandaneto</code></a>! - Normalize capture timestamp overrides to equivalent UTC ISO strings in the browser and Node.js SDKs and shared core. (2026-08-14)</li> <li>Updated dependencies [<a href="https://github.com/PostHog/posthog-js/commit/0a0206f907f4b58dc28f36aa1fc441b55c489faf"><code>0a0206f</code></a>]: <ul> <li><code>@posthog/core</code><a href="https://github.com/1"><code>@1</code></a>.48.1</li> </ul> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/PostHog/posthog-js/commit/6872a1c5e4df0917dc0a72cca4a597d9b4d72803"><code>6872a1c</code></a> chore: update versions and lockfile [version bump]</li> <li><a href="https://github.com/PostHog/posthog-js/commit/0a0206f907f4b58dc28f36aa1fc441b55c489faf"><code>0a0206f</code></a> fix: normalize SDK timestamps to UTC (<a href="https://github.com/PostHog/posthog-js/tree/HEAD/packages/node/issues/4521">#4521</a>)</li> <li>See full diff in <a href="https://github.com/PostHog/posthog-js/commits/posthog-node@5.49.1/packages/node">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>

Bumps the npm-major group with 2 updates: [jose](https://github.com/panva/jose) and [@tsconfig/bun](https://github.com/tsconfig/bases/tree/HEAD/bases). Updates `jose` from 6.2.8 to 6.2.9 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/panva/jose/releases">jose's releases</a>.</em></p> <blockquote> <h2>v6.2.9</h2> <h3>Fixes</h3> <ul> <li>reject a JWE whose generated Key Management Parameters collide (<a href="https://github.com/panva/jose/commit/6ed19a6a9798a7d55a647958b4ee816c4b77627d">6ed19a6</a>)</li> <li><strong>types:</strong> undeprecate PBES2 p2c parameter (<a href="https://github.com/panva/jose/commit/33bf832986d21cce0336b27441e3588499a70d67">33bf832</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/panva/jose/blob/main/CHANGELOG.md">jose's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/panva/jose/compare/v6.2.8...v6.2.9">6.2.9</a> (2026-08-15)</h2> <h3>Fixes</h3> <ul> <li>reject a JWE whose generated Key Management Parameters collide (<a href="https://github.com/panva/jose/commit/6ed19a6a9798a7d55a647958b4ee816c4b77627d">6ed19a6</a>)</li> <li><strong>types:</strong> undeprecate PBES2 p2c parameter (<a href="https://github.com/panva/jose/commit/33bf832986d21cce0336b27441e3588499a70d67">33bf832</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/panva/jose/commit/f3a3c780b9bd8d7d25cb7c5dd5d4e57164d4fbfc"><code>f3a3c78</code></a> chore(release): 6.2.9</li> <li><a href="https://github.com/panva/jose/commit/33bf832986d21cce0336b27441e3588499a70d67"><code>33bf832</code></a> fix(types): undeprecate PBES2 p2c parameter</li> <li><a href="https://github.com/panva/jose/commit/6ed19a6a9798a7d55a647958b4ee816c4b77627d"><code>6ed19a6</code></a> fix: reject a JWE whose generated Key Management Parameters collide</li> <li><a href="https://github.com/panva/jose/commit/944840d16704db727fad2bfaa8385e95b0a52bfe"><code>944840d</code></a> ci: use shared release workflows</li> <li><a href="https://github.com/panva/jose/commit/05bccf239936a0bc0892f32ca86ff079585f5d13"><code>05bccf2</code></a> chore: bump packages</li> <li><a href="https://github.com/panva/jose/commit/f7392d1217ee506cf15a0c4aaadf22f9c8c07db8"><code>f7392d1</code></a> test: account for workerd nodejs_compat flag default changes</li> <li><a href="https://github.com/panva/jose/commit/4e944be71e9bb44704702327fc3c163e93de21c4"><code>4e944be</code></a> ci: drop the wait-for-npm machinery</li> <li><a href="https://github.com/panva/jose/commit/4285b6f411e2f7f1ac09f7fd97ef836dda01981b"><code>4285b6f</code></a> chore(deps-dev): bump undici</li> <li><a href="https://github.com/panva/jose/commit/cb114ecde718b06423c426109454b418e5d76497"><code>cb114ec</code></a> chore: cleanup after release</li> <li>See full diff in <a href="https://github.com/panva/jose/compare/v6.2.8...v6.2.9">compare view</a></li> </ul> </details> <br /> Updates `@tsconfig/bun` from 1.0.10 to 1.0.11 <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/tsconfig/bases/commits/HEAD/bases">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>

## Summary - Bump `@supabase/pg-delta` from `1.0.0-alpha.42` to `1.0.0-alpha.46` so `db diff`, `db pull`, and `db schema declarative generate` pick up supabase-profile parameter-ACL filtering, `OWNED BY` with the owning table, per-statement load fallback, `vault_presence`, and reconnect-on-stuck load assist. - Delete the CLI copy of platform parameter-ACL filtering; the engine profile now owns that coverage. - Pretty-print generated SQL by default (uppercase keywords, indent 2, aligned columns). - Prepare declarative shadows only when files recreate image defaults (`pgjwt` / `pgcrypto` / `uuid-ossp`); omit means keep. Restore image `pgjwt` after a pgcrypto-only drop only if it was installed. On PG14, detach `storage.objects.id` before dropping `uuid-ossp`. - CREATE EXTENSION detection is `--` / `/* */` / simple `'...'` plus a regex (pathological SQL is an accepted miss). Prep uses `pool.query`; a locked DROP can delay Ctrl-C like other sites. Extracted from #6274 so the engine upgrade can land on `develop` without the schema-first command stack. ## Linked issue Supabase maintainer change; no public issue to close. - [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. `feat(cli): …`). - [x] Tests added or updated for the change. - [x] `pnpm check:all` and `pnpm test` pass for the workspace(s) I touched.

## Summary Collocate remote-platform golden-path tests beside the commands they cover in apps/cli, while keeping Docker-stack-only scenarios as ordinary e2e tests and leaving the apps/cli-e2e replay and recording suite unchanged. Use one serial live Vitest project with a single extended test fixture. Global setup requires a Management API URL and access token, provisions one disposable project through the typed Effect API client, waits with bounded retry semantics, derives the platform tenant host from project metadata, and shares cli plus project fixtures with every test. Explicit live runs fail fast when configuration is missing; there are no capability gates or runtime skips. Keep live coverage intentionally narrow: one representative golden path per covered command. Setup and teardown may invoke other commands, but assertions stay focused on the command under test. Exact owned resources are cleaned even after ambiguous command results, and target plus cleanup failures are preserved. Move the eight local Docker-stack suites to e2e naming, including functions dev synchronization on observable reload completion. The standalone live workflow retains Docker preflight, serial execution, one attempt, a 20-minute limit, and scoped project sweeping.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 643b182881

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

## TL;DR fixes `supabase db reset` and `supabase start` hanging forever with no error when the database connection dies while migrations are being applied ## whats broken? node-postgres silently discards every protocol frame once a socket stops being writable, while still reporting the write as successful, so the whole batch goes nowhere and the CLI waits forever on a reply the server was never asked for it also leaves TCP keepalive off by default, where the Go CLI's driver had it on, so a peer that dies without a FIN or RST is never noticed either ## fixed now by: - failing a batch that never reached the wire as a connection error, carrying the driver's own reason instead of blaming the migration's first statement - discarding that pooled connection, so the next batch redials instead of writing into the same dead socket - turning TCP keepalive on for every connection the CLI opens, so a silently dead peer is eventually detected instead of waited on a server that stays alive but never answers still waits, matching the Go CLI, since that is indistinguishable from a long running statement ## ref: - closes: #6244

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 11878ae318

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

## What Stacked on #6311. Applies the same exercise to knip: replaces the per-package nx-inferred knip targets with knip's native monorepo support, so `pnpm exec knip-bun` from the repo root just works and knip gains cross-workspace awareness. ## Why Same rationale as #6311 — knip configuration lived in per-package `package.json` `knip` objects wired together by an nx plugin, and per-package runs couldn't see across workspace boundaries. The root run immediately proved the point: knip itself flagged ~15 pieces of now-dead config that the per-package setup required, including every `ignoreBinaries: ["nx"]` entry (per-package runs couldn't resolve the root `nx` devDependency; a root run can), four stale `ignoreDependencies` in `apps/cli`, and `packages/api` entry patterns its own package.json `exports` already imply. `packages/config` needs no knip config at all anymore. ## Key changes - Root `knip.json` using the `workspaces` map, absorbing each package's former `knip` object; the `--exclude catalogReferences` CLI flag moves into the config (`exclude`). - New root-workspace surface configured explicitly: `.github/scripts` and `tools/release` as entries, `apps/cli-go/**` ignored, `verdaccio`/`go` ignored (referenced via spawn paths knip cannot trace), and `apps/docs`'s `mdx-components.tsx` convention entry. - `knip:check`/`knip:fix` are plain command targets on `@supabase/root`; `knip.plugin.ts` is deleted; the `knip` devDependency and config object are removed from every package (root devDependency only). - `docs/nx-inference-plugins.md` now documents only the remaining typescript/test/go plugins. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com> Co-authored-by: Julien Goux <hi@jgoux.dev>

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dcc9e12d7f

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

…t (CLI-2231) (#6315) ## Summary Splits `@supabase/config`'s public surface into three strictly layered entrypoints, per [CLI-2231](https://linear.app/supabase/issue/CLI-2231/refactor-config-package-to-default-export-node-with-effect-as-subpath) (including its 2026-08-24 amendment for browser consumers): - **`.` — pure, browser-safe.** Schema, types, document encode functions, defaults/sparse mapping, error classes, and constants only. No Effect-returning functions are exported, and no `@effect/platform-*`, `node:`, or `bun:` module can enter its transitive graph — Studio (see supabase/supabase#48906) can bundle this platform-free. The pure document layer was physically partitioned out of `io.ts`/`functions-manifest.ts` (new `config-document.ts`, `functions-manifest-model.ts`) so the invariant is structural, and a static import-graph test (`entrypoint-purity.unit.test.ts`) enforces it: file allowlist, bare-specifier allowlist (`effect`/`smol-toml`/`dedent`), dynamic-`import()`/`require` detection, and inline-snapshot pinning of both export surfaces. Browser bundle drops 387 KB → ~355 KB with zero file-IO code reachable. - **`./effect` — Effect-native superset.** Re-exports everything in `.` plus the Effect-native surface (`loadProjectConfig`, `saveProjectConfig`, discovery, env loading, `inferFunctionsManifest`, `ProjectConfigStore`, `projectConfigStoreLayer`, …), so Effect-native consumers need one specifier (Option B from the issue). The 22 `apps/cli` files that import Effect-native symbols were repointed with byte-identical symbol lists; the other 37 consumer files keep the bare specifier unchanged. On the issue's open decision: `resolveProjectValue`/`resolveProjectSubtree` stay Effect-typed in `./effect` only (the amendment requires `.` to carry plain-sync signatures; unwrapping can be revisited in CLI-2234). - **`./io` — Promise facade for non-Effect consumers**, replacing the unused `./bun`/`./node` subpaths (verified zero consumers) with `bun`/`node`/`browser`/`default` export conditions. The `browser` condition resolves to a side-effect-free stub exporting the same seven names, each rejecting at invocation with a pointer to `.`, instead of dragging `@effect/platform-node` into a browser bundle (kept side-effect-free so isomorphic/edge bundles that never call config IO still build and load). All three condition targets re-export the pure surface, so `./io` consumers never need a second specifier for parameter/return types. Both facades now share one lazily built `ManagedRuntime` via a common factory — previously each call did `ManagedRuntime.make(...)` fresh and never disposed it — and the runtime layer is narrowed to `FileSystem + Path` (the former full `*Services.layer` attached a permanent `process.stdin` listener via Terminal). - **`./schema.json`** — unchanged. Dependency reshape: `effect` moves to `peerDependencies` — Effect v4 resolves services by string key, so this isn't about tag identity; the real grounds are a single `effect` version across the dependency graph while rc-to-rc internals churn, dedupe/bundle size, and letting the consumer own the version — and `@effect/platform-bun`/`-node` become optional peers (a consumer only needs the one matching their runtime), each mirrored in `devDependencies` for local build/test. `dedent` and `smol-toml` stay regular dependencies. Docs: ADR 0009's open "config package architecture" bullet is resolved with the entrypoint contract, and `packages/config/AGENTS.md` records the monorepo import rule (Effect symbols → `/effect`; pure-only → `.`; `./io` is for external non-Effect consumers only). Out of scope (tracked separately): npm publishing/compiled dist output (CLI-2232/CLI-2233) and the public-surface audit (CLI-2234). ## Linked issue Linear: [CLI-2231](https://linear.app/supabase/issue/CLI-2231/refactor-config-package-to-default-export-node-with-effect-as-subpath) - [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] `pnpm check:all` and `pnpm test` pass for the workspace(s) I touched.

- extends: #6017 - follows the same pattern as: supabase/supabase#47846

…fig (CLI-2235) (#6328) ## Summary Repo-wide vocabulary rename settling `@supabase/config`'s core naming before first npm publish ([CLI-2235](https://linear.app/supabase/issue/CLI-2235/rename-config-document-type-projectconfig-cliconfig-free-projectconfig)). One prefix rule across the package: **`Cli*` = the local checkout side; bare `Project*` = the hosted Supabase project.** After this PR no exported name uses a bare "project" to mean the local checkout, and `ProjectConfig` is freed for the hosted-project subset type the API-mapping work (CLI-2230 / CLI-2156) will introduce. Renames are only free while the package is `private: true`, which is why this blocks CLI-2169 (first publish). No functional behavior changes: the config-file surface (`project_id`, section names), the generated `schema.json`, and the schema URL value are unchanged. **Four renamed error tags are user-visible and change deliberately with this release**: the stderr and `--output-format json` error code changes (`ProjectConfigParseError`→`CliConfigParseError`, `ProjectEnvParseError`→`CliProjectEnvParseError`, `MissingProjectConfigValueError`→`MissingCliConfigValueError` on malformed-config/env failures, and `ProjectHomeNotDirectoryError`→`CliProjectHomeNotDirectoryError` when `.supabase/` is blocked by a file or symlink loop), and the telemetry `error_fingerprint` series fork accordingly (`tag:<old>` goes flat, `tag:<new>` starts) — annotate dashboards/alerts keyed on the old values at release. A `normalize-error` unit test now pins the user-facing codes so the next such rename is a visible review event. Service tag strings were renamed with their services (app-internal identity keys) and moved out of the package's namespace: `supabase/config/*` → `supabase/cli/*` for all apps/cli-owned services. ADRs 0009/0018/0019 keep their pre-rename symbol names as historical records — the tables below are the mapping. ### Step 0 — free the `CliConfig` name (apps/cli) | Old | New | | --- | --- | | `CliConfig` (service, tag `supabase/config/CliConfig`) | `CliSettings` (tag `supabase/cli/CliSettings`) | | `LegacyCliConfig` (tag `supabase/legacy/CliConfig`) | `LegacyCliSettings` (tag `supabase/legacy/CliSettings`) | | `cliConfigLayer`, `mockCliConfig`, `cliConfig` vars, … | `cliSettingsLayer`, `mockCliSettings`, `cliSettings`, … | | `cli-config.service.ts` / `cli-config.layer.ts` / `legacy-cli-config.*` | `cli-settings.*` / `legacy-cli-settings.*` | ### Config-document family (`ProjectConfig*` → `CliConfig*`) | Old | New | | --- | --- | | `ProjectConfig`, `ProjectConfigSchema`, `ProjectConfigJson`, `toProjectConfigJsonSchema` | `CliConfig`, `CliConfigSchema`, `CliConfigJson`, `toCliConfigJsonSchema` | | `loadProjectConfig`, `loadProjectConfigFile`, `saveProjectConfig`, `LoadedProjectConfig`, `Load/SaveProjectConfigOptions` | `loadCliConfig`, `loadCliConfigFile`, `saveCliConfig`, `LoadedCliConfig`, `Load/SaveCliConfigOptions` | | `encodeProjectConfigToJson/Toml`, `projectConfigValueSourceAt`, `ProjectConfigValueOrigin/Source` | `encodeCliConfigToJson/Toml`, `cliConfigValueSourceAt`, `CliConfigValueOrigin/Source` | | `ProjectConfigParseError`, `MissingProjectConfigValueError` | `CliConfigParseError`, `MissingCliConfigValueError` | | `ProjectConfigStore`, `projectConfigStoreLayer` (+ file renames) | `CliConfigStore`, `cliConfigStoreLayer` (`cli-config.service.ts` / `cli-config.layer.ts`) | | `PROJECT_CONFIG_SCHEMA_URL` (value unchanged) | `CLI_CONFIG_SCHEMA_URL` | | `getDefaultProjectConfig`, `subtractProjectConfig` | `getDefaultCliConfig`, `subtractCliConfig` | | compounds re-grepped post-CLI-2231: `writeProjectConfig`, `decodeProjectConfig`, `ProjectConfigIo`, `loadFunctionsProjectConfig`, `renderProjectConfigTemplate`, `BaseProjectConfig`, `SparseProjectConfig`, … | same names with `CliConfig` substituted | ### Local-checkout family (`Project*` → `CliProject*`) | Old | New | | --- | --- | | `ProjectEnvironment`, `loadProjectEnvironment(For)`, `LoadProjectEnvironmentOptions`, `LiveProjectEnvironment` | `CliProjectEnvironment`, `loadCliProjectEnvironment(For)`, … | | `ProjectPaths`, `findProjectPaths(For)`, `FindProjectPathsOptions`, `findProjectRoot(For/FromRepoState)` | `CliProjectPaths`, `findCliProjectPaths(For)`, …, `findCliProjectRoot(…)` | | `ProjectEnvParseError` | `CliProjectEnvParseError` | | `resolveProjectValue(AtPath)`, `resolveProjectSubtree`, `ResolvedProjectValue`, `ResolveProjectOptions` — config family: they resolve `env()` refs in config values | `resolveCliConfigValue(AtPath)`, `resolveCliConfigSubtree`, `ResolvedCliConfigValue`, `ResolveCliConfigOptions` | | `ProjectContext` (apps/cli, tag `supabase/config/ProjectContext`) + `projectContextLayer(For)`, `mockProjectContext`, … + file renames | `CliProjectContext` (tag `supabase/cli/CliProjectContext`) + `cliProjectContextLayer(For)`, `mockCliProjectContext`, … (`cli-project-context.*`) | | `ProjectHome` (apps/cli) + `projectHomeLayer(For)`, `ProjectHomeNotDirectoryError`, … + file renames | `CliProjectHome` (tag `supabase/cli/CliProjectHome`) + `cliProjectHomeLayer(For)`, … (`cli-project-home.*`) | | `ProjectLocalServiceVersions` (apps/cli) + layer/mocks + file renames | `CliProjectLocalServiceVersions` (tag `supabase/cli/CliProjectLocalServiceVersions`) (`cli-project-local-service-versions.*`) | | `projectCommandBaseLayer`, `provideProjectCommandRuntime` (apps/cli) | `cliProjectCommandBaseLayer`, `provideCliProjectCommandRuntime` | | `LoadCliConfigOptions.projectEnv` (published options field) + the `resolveCliConfig*` resolvers' `projectEnv` param | `cliProjectEnv` (apps/cli-internal `CliProjectContext.projectEnv` deliberately keeps its name — filed on CLI-2234) | ### Deliberately unchanged - `DuplicateRemoteProjectIdError` / `InvalidRemoteProjectIdError` — "project id" there genuinely means the hosted project ref (the *new* meaning of "project"). (`remoteProjectConfig`, initially kept under the same carve-out, was renamed to `remoteCliConfigBlock` per review — it binds the reserved `ProjectConfig` spelling for what is a `CliConfig` sub-document.) - `packages/api` generated names (`v2GetProjectConfig`, …) — hosted-project endpoint operations. - Legacy-internal `Legacy*` / `legacy*ProjectEnv*` / `LegacyLocalProjectContext` symbols — already namespaced by their `Legacy` prefix and pending deletion with the legacy shell. - Go-source provenance comments (`getProjectRoot`, `internal/utils/misc.go`) and `apps/cli-go/**`. ### Docs `packages/config/docs/project-config-loading.md` — the doc that defined the old vocabulary — is rewritten as `cli-config-loading.md` around the final naming, with stale behavioral claims corrected against current source along the way: - missing `env(NAME)` resolution does not fail with `MissingProjectEnvVarError` (that class doesn't exist); the resolvers leave unresolved literals as plain strings - `loadCliConfig` substitutes most `env(NAME)` refs eagerly at load; only `functions.<name>.env.*` stays literal for on-demand resolution - `supabase init` writes a commented `config.toml` template, not a `$schema`-only `config.json` - managed-stack state lives under global `SUPABASE_HOME`, not repo-local `.supabase/` ## Review round 1 (2026-08-25) Addressed from the multi-pass review: - **Truthful user-visible statement** (above) + `normalize-error` unit test pinning the error codes. - **Finished the vocabulary in `apps/cli/src/next/config/`**: `CliProjectHome`, `CliProjectLocalServiceVersions`, `cliProjectCommandBaseLayer`/`provideCliProjectCommandRuntime`. Remaining bare `Project*` there (`ProjectLinkRemote`, `ProjectLinkState`, `ProjectRefResolver`) describe the hosted project or the link to it — now stated in the vocabulary doc. - **Retagged all apps/cli services out of the package's namespace**: `supabase/config/*` → `supabase/cli/*` (each tag literal verified single-occurrence). - **`remoteProjectConfig` → `remoteCliConfigBlock`**; `LoadCliConfigOptions.projectEnv` → `cliProjectEnv` (+ resolver params). - **ADR 0009/0018**: dated rename addenda (old→new tables + pointer to the vocabulary doc); ADR bodies untouched. - **Docs**: README vocabulary blockquote; vocabulary doc gains the `/io` facade section, `LegacyCliSettings` bullet, `project_id` dual-meaning note, corrected `SUPABASE_HOME` keying + `identity.json` inventory; CLI-2110 plan doc symbols updated; `packages/stack/README.md` `cliSettings.supabaseHome`; stale comment fixes (`paths.ts`, `project.unit.test.ts`, `push.handler.ts`, `run.ts` defect strings). Filed as explicit pre-publish decisions rather than rushed here: `/io` facade naming convention → [CLI-2234](https://linear.app/supabase/issue/CLI-2234); `BaseCliConfig` as the hosted-diff operand type → [CLI-2230](https://linear.app/supabase/issue/CLI-2230). ## Linked issue [CLI-2235](https://linear.app/supabase/issue/CLI-2235/rename-config-document-type-projectconfig-cliconfig-free-projectconfig) - [x] I'm a Supabase maintainer working from a Linear ticket. - [x] The PR title follows [Conventional Commits](https://www.conventionalcommits.org/).

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7b2f02df72

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

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>

…6260) ## Summary Adds the `[workers]` section to the project config schema: a `Schema.Record` of worker name to `{ runtime, size, instances, source }`, mirroring the `[functions.<slug>]` convention in the same file. The same schema is used for the project config and for `[remotes.*]`, so a remote can carry its own worker overrides. Two constraints live at the schema level: - **Worker names are DNS labels**, matching what the Management API validates its `:name` path parameter against, since they end up in hostnames. - **`instances` is a non-negative integer**, matching `spec.instances` in the API's own input schema. A value that gets past the schema is dropped rather than sent, so leaving it unbounded means a `push` silently deploys a different count than the config asked for. There is no project-wide scalar in the table — an earlier revision had a `[workers] root` for relocating the grouping directory, and it was dropped because `[workers.<name>] source` already puts a worker anywhere in the repo. That keeps `workers` a plain record with nothing for the index signature to collide with, rather than a `StructWithRest` needing a key-pattern exclusion that vanished under the `disableChecks: true` `io.ts` uses for unselected remotes. No CLI surface consumes this yet — it lands first so the schema and its generated types are reviewable on their own. **Stack 1 of 4.** Followed by `workers new` (#6261), `workers push` (#6262), and `workers list`/`status`/`delete` (#6263). ## 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>

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4b5d8bec0b

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

…config paths (#6330) ## What changed - **VSCode**: ignore `.repos/` (the vendored `effect` source checkout) in file explorer, search, and file watchers so the editor doesn't index or watch the submodule contents. - **oxc**: replace the `--disable-nested-config` flag with explicit `--config` paths (`.oxlintrc.json`, `.oxfmtrc.json`) in the Nx `lint:*`/`fmt:*` targets, and add the same explicit config paths to the oxc VSCode extension settings. ## Why `.repos` submodules were being picked up by the VSCode extensions and editor indexing. Pointing oxlint/oxfmt at explicit root configs (instead of relying on nested-config discovery) and excluding `.repos` from the editor keeps the vendored repos from being loaded at all. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4256526bdf

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

## TL;DR Unblocks the production deploy: fixes the three new CodeQL alerts gating it and the container leak codex flagged on the same PR.... > [!NOTE] > the shadow cache key derivation change means every existing cached baseline goes cold once after upgrade, one full re-export per settings combination, old tars age out via the normal retention sweep. a slower first run post-upgrade is expected, not a regression.... ## ref: * unblocks: [https://github.com/supabase/cli/pull/6321](<https://github.com/supabase/cli/pull/6321>)

## Summary - Move TypeScript unit, integration, and end-to-end execution to package-local Vitest scripts orchestrated by Turbo while keeping live tests separate. - Run unit and integration suites in independent CI jobs so integration tests can be sharded separately later. - Apply each end-to-end shard to every package that owns an e2e suite, executing packages sequentially within a runner. - Encode Go and CLI build prerequisites for local e2e entrypoints, then isolate Vitest passthrough arguments from those build tasks. - Keep Go unit tests package-local and in their dedicated race-and-coverage workflow while the root Vitest fan-out remains uniformly shardable. - Right-size the unit job to a 4-vCPU Blacksmith runner without preemptively capping workers. - Remove the `test:core` alias and document explicit unit and integration commands. ## Context The first e2e shard previously ran every non-CLI-harness e2e suite unsharded, making it consistently much slower than the other shards. Propagating the same Vitest shard to each package distributes those suites uniformly. Turbo currently provides only the test task graph and prerequisite ordering. Test caching remains disabled until its inputs and outputs are designed separately.

… convention (#6335) ## What changed Records the `@supabase/config` naming convention (decided 2026-08-24, applied mechanically by CLI-2235 / #6328) as normative documentation: - **New [ADR 0020](docs/adr/0020-config-naming-vocabulary.md)** — the vocabulary decision and rationale: `CliConfig` = the full config-file document (`supabase/config.toml`/`.json`, the local superset), `ProjectConfig` = the hosted-project subset (a sparse overlay of the hosted sections, being introduced by CLI-2230), `CliSettings` = the CLI's own runtime settings (formerly named `CliConfig`), plus the prefix rule: `Cli*` = the local checkout side, bare `Project*` = the hosted Supabase project, and value-helpers follow the config family regardless of their inputs (`resolveCliConfigValue`, `MissingCliConfigValueError`). - **Repo-root `AGENTS.md`** — new "Config Naming Vocabulary" section so agent/human sessions load the convention at start instead of re-deriving it from PR history. - **`packages/config/README.md`** — the intro blockquote becomes a proper "Naming" section (public contract documentation once the package publishes). - **`packages/config/docs/cli-config-loading.md`** — the Vocabulary section already *used* the settled names; this adds the prefix rule stated *as a rule*, linking ADR 0020. (The issue referenced this file by its pre-CLI-2235 name `project-config-loading.md`.) Stale-vocabulary sweep across `*.md` came back clean: ADRs 0009/0018 already carry CLI-2235 rename addendums and stay untouched as historical records, and every remaining `CliConfig` hit (including legacy `SIDE_EFFECTS.md` files) uses the current document-family meaning. ## Why Renames are free only while `packages/config` is `private: true` — CLI-2169 flips it public, and Studio is already an external consumer waiting on the package (supabase/supabase#48906). The vocabulary drifted once before (`CliConfig` meant the settings service, `ProjectConfig` meant the document); without a recorded decision it would drift again. ## Reviewer context Coordinated with the in-flight CLI-2230 branch: it owns the `ProjectConfig: reserved…` vocabulary bullet in `cli-config-loading.md` and will add a "ProjectConfig mapping" README subsection after this PR's "Naming" section, updating the "introduced by CLI-2230 (in flight)" sentence when it lands. `BaseCliConfig` is deliberately never cited as a prefix-rule example — its name is under an open ruling on CLI-2230. Fixes CLI-2238

## Summary - Add explicit TypeScript type-check and Go lint leaf scripts, with repository-wide quality orchestration owned exclusively by the root Turbo configuration. - Keep oxlint, oxfmt, and knip root-owned and uncached; packages expose no quality aggregation or Turbo quality commands. - Remove the unused TypeScript Nx inference plugin and update API formatting workflows and contributor guidance while retaining Nx build/live orchestration. ## Context Quality leaf scripts remain the source of truth, while only the monorepo root invokes Turbo to compose them into repository-wide checks. This keeps package boundaries independent of the orchestrator and preserves the build and live workflows still owned by Nx.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: aa667a1f42

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

## Summary - move Go CLI, TypeScript CLI, config, API, and docs build/generation orchestration from Nx to root-owned Turbo tasks - model explicit cross-workspace dependencies, toolchain inputs, and generated/build outputs for safe local cache restoration - replace workflow CLI builds and update contributor docs while retaining the uncached Nx live/auxiliary bridge for the follow-up migration ## Context This follows the root quality migration merged in #6336 and preserves its root-only quality architecture. Deterministic Go, CLI, config, and docs tasks cache exact outputs; API generation remains uncached because it fetches live OpenAPI documents, and the root generation entrypoint orders API generation before docs generation.

…#6337) ## Summary The 2026-05-30 flip of `[api].auto_expose_new_tables` (#5524) made *unset* mean "revoke the default Data API GRANTs on new `public` entities", anticipating a cloud default change that never landed — platform projects still auto-expose new entities. A local stack bootstrapped with the flag unset therefore diverged from remote and polluted the user's first `db diff` with spurious GRANT/REVOKE noise. This flips the effective default back so local matches the platform: - **unset ≡ explicit `true`** → keep the bundled initial-schema GRANTs (auto-expose), at every consumer: next `start`, legacy `legacyApplyApiPrivileges`, and the shadow-db / pg-delta cache keys (unset and `true` now hash identically, so a no-op config edit can't force a re-snapshot). - **explicit `false`** → run the revoke SQL, matching a cloud project with the "Default privileges for new entities" toggle turned off. - The deprecation warning and the 2026-10-30 removal narrative are removed from both shells, the init template, the schema description, and `db start`'s `SIDE_EFFECTS.md`, since their premise collapsed. - The field stays a tri-state optional key, so `config push` keeps sending it omitempty and unset stays distinguishable. The init template documents the `true` default as a commented example; fresh projects stay on the unset fallback. Reviewer notes: - Users with the flag unset take a one-time shadow re-snapshot (~90MB) because the baked cluster genuinely changes (the revoke SQL no longer runs). Cache keys diverging from Go-era `.temp/pgdelta` entries is intentional for the same reason. - Volumes initialized under the unset-means-revoke era keep their revoked GRANTs until a `db reset`/fresh volume; this change only affects new setups. - `apps/cli-go` is intentionally untouched (residual delegation surface). `apps/docs/public/cli/config.schema.json` gets a surgical description edit only — the committed file is already stale at HEAD for unrelated toolchain reasons (oxfmt version drift + effect rc `$ref` inlining), so a full regen is left for its own commit. ## Linked issue Closes # — none; Supabase maintainer working from an internal report. - [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] `pnpm check:all` and `pnpm test` pass for the workspace(s) I touched. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

## Summary - move live, recording, smoke, and docs-development orchestration from Nx metadata to uncached root-owned Turbo tasks backed by leaf package scripts - express the live and recording CLI build dependencies and the docs generation prerequisite directly in the Turbo graph - update the live workflow and current contributor guidance while retaining dependency-only Nx metadata for graph inspection ## Context This follows #6342, which is now merged into develop. Nx packages, configuration, and the Go inference plugin remain intentionally for the dedicated CLI-2258 removal.

## TL;DR adds live e2e coverage for functions download, closing the functions `management` command family. ## whats introduced? - full artifact round trip against the provisioned live project: deploy a function carrying a unique marker, delete the local source, download it back, assert the marker survived - the output directory is pre-created host-owned because the unbundle container runs as root and would otherwise leave a directory the CI runner cannot remove at teardown - a positive assertion on the docker path banner, so a silent fallback to the server-side extractor fails the run instead of passing vacuously - the AGENTS.md live carve-out now names functions download next to functions deploy ## ref: - extends: #5588

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 997a1e69a4

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

avallete and others added 30 commits August 18, 2026 12:27

7ttp mentioned this pull request Aug 25, 2026

chore(codeql): resolve deploy scan findings #6326

Merged

chatgpt-codex-connector Bot reviewed Aug 25, 2026

View reviewed changes

Comment thread packages/stack/src/BinaryResolver.ts

Comment thread apps/cli/src/legacy/shared/db-bootstrap/pgdata-snapshot.ts

Comment thread apps/cli/src/next/commands/functions/dev/dev.e2e.test.ts

chatgpt-codex-connector Bot reviewed Aug 25, 2026

View reviewed changes

Comment thread apps/cli/src/legacy/shared/db-bootstrap/pgdata-snapshot.ts

chatgpt-codex-connector Bot reviewed Aug 25, 2026

View reviewed changes

Comment thread apps/cli/src/legacy/shared/db-bootstrap/shadow-database.ts

Comment thread packages/stack/src/managed/control.ts

Comment thread packages/stack/src/createStack.ts

Coly010 and others added 3 commits August 25, 2026 12:02

fix(cli): cap kong dns cache ttls (#6324)

38f31b4

- extends: #6017 - follows the same pattern as: supabase/supabase#47846

chatgpt-codex-connector Bot reviewed Aug 25, 2026

View reviewed changes

Comment thread packages/stack/src/managed/ids.ts

supabase-cli-releaser Bot and others added 2 commits August 25, 2026 19:25

chatgpt-codex-connector Bot reviewed Aug 25, 2026

View reviewed changes

Comment thread apps/cli/src/shared/functions/serve.ts

Comment thread knip.json

chatgpt-codex-connector Bot reviewed Aug 26, 2026

View reviewed changes

Comment thread apps/cli/src/legacy/shared/legacy-migration-apply.ts

Comment thread packages/stack/src/services/postgres-init.ts

Comment thread packages/stack/src/BinaryResolver.ts

Comment thread packages/stack/src/services/postgres.ts

Comment thread packages/stack/src/managed/document.ts

7ttp and others added 4 commits August 26, 2026 08:47

chatgpt-codex-connector Bot reviewed Aug 26, 2026

View reviewed changes

Comment thread packages/stack/src/ContainerRuntime.ts

Comment thread packages/stack/src/StackPreparation.ts

jgoux and others added 4 commits August 26, 2026 13:17

github-advanced-security Bot found potential problems Aug 26, 2026

View reviewed changes

Comment thread apps/cli/src/legacy/commands/functions/download/download.live.test.ts Dismissed

chatgpt-codex-connector Bot reviewed Aug 26, 2026

View reviewed changes

Comment thread packages/config/src/io.ts

Comment thread packages/config/src/io.unit.test.ts

avallete approved these changes Aug 26, 2026

View reviewed changes

avallete self-requested a review August 26, 2026 19:34

avallete approved these changes Aug 26, 2026

View reviewed changes

supabase-cli-releaser Bot merged commit 997a1e6 into main Aug 26, 2026
68 of 69 checks passed

Uh oh!

Conversation

supabase-cli-releaser Bot commented Aug 25, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants