Skip to content

chore: production deploy - #7653

Open
supabase-cli-releaser[bot] wants to merge 23 commits into
mainfrom
develop
Open

supabase-cli-releaser[bot] wants to merge 23 commits into
mainfrom
develop

Conversation

@supabase-cli-releaser

Copy link
Copy Markdown
Contributor

grdsdev and others added 2 commits November 16, 2026 18:08
…en 0.4.0 (#7608)

## Summary

`supabase gen types --lang swift` now builds the `supabase-typegen`
generator from supabase-swift's source, through `@supabase/typegen`
0.4.0 (SDK-3045, supabase/sdk#361). This PR does two things:

1. **Passes `HOME` and `XDG_CACHE_HOME` to the Swift driver.** The
driver reads them from the filtered environment the generator layer
gives it, to find its cache of built binaries. Before this PR, the layer
passed only `PATH`, `PATHEXT` and `ComSpec`. The cache path became
relative and resolved against the working directory, so binaries landed
inside the user's project. Other languages do not change: the spawned
tool already inherits the full environment, and the Dart driver reads
nothing from this object.
2. **Bumps `@supabase/typegen` from 0.3.4 to 0.4.0.** With it, the Swift
driver:
- builds `supabase-typegen` from source at a supabase-swift commit, and
caches the binary by commit. It no longer downloads a prebuilt binary;
- picks the commit from the new `--swift-typegen-source
<version|branch|sha|path>` flag, else from the supabase-swift pin in the
nearest `Package.resolved`, else from the latest 3.x release (with a
notice on stderr);
- drops `SUPABASE_TYPEGEN` and the `PATH` fallback. The flag's
local-path form covers what `SUPABASE_TYPEGEN` did.

The CLI needs no code for the new flag. It renders language flags from
the registry's option specs, so `--swift-typegen-source` appears with
the bump, like `--swift-access-control`. Like every language flag, it is
in the mutex group with `--remote`, `--linked` and `--project-ref`.

The driver change is not marked as breaking. The Swift generator is
still alpha in supabase-swift, so 0.4.0 is a minor bump.

## Linked issue

Linear: CLI-3138 (replaces CLI-3134). Driver: SDK-3045.

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

## How it was tested

- End to end, with the CLI from this branch (`bun apps/cli/src/main.ts
gen types --lang swift --db-url …`), a Postgres 17 container with a
table, an enum, a view and a function, and Swift 6.4 on macOS. The cache
was a fresh `XDG_CACHE_HOME`.

  | Case | Result |
  | -- | -- |
| `--swift-typegen-source main`, no `Package.resolved` | Built
supabase-swift `main` (`f4f132a`) from source in 212 s, cached it, and
printed the `@Table` structs, the enum and the function. |
| Same, again, with `--swift-access-control public` | Used the cached
binary in 2 s. The output is `public`. |
| `Package.resolved` two levels up pins `main` at `f4f132a` | `Using
branch main at f4f132a…, pinned in ../../Package.resolved.` Cached, 2 s,
same output. |
| No pin, no flag | Fails: supabase-swift has no 3.x release yet. The
message names `--swift-typegen-source`. |
| `--swift-typegen-source f4f132a` | Fails before git runs: an
abbreviated SHA is refused. |
| `--swift-typegen-source 3.0.0-alpha.1` | Fails: no tag
`v3.0.0-alpha.1` yet. |
| `--swift-typegen-source ./supabase-swift` (a clone) | Built in the
checkout in 203 s. Same output as the other builds. The checkout has no
git changes after the build. |

No run wrote files into the project folders, and no scratch folders were
left in `$TMPDIR`.

- Unit and integration tests:
- `types.generator.integration.test.ts` runs a fake `supabase-typegen`
from the cache under `XDG_CACHE_HOME`, and under `HOME`. The cache is
now keyed by the pinned commit SHA.
- `types.integration.test.ts` checks that `--swift-typegen-source`
reaches the generator, and that it is rejected with `--project-ref`.
- `types.generator.unit.test.ts` checks that only the Swift generator
gets the flag.
- All unit tests pass (7655). The integration tests for
`src/commands/gen` pass (271).
- In the full integration run, 3 TLS tests in
`db-connection.sql-pg.integration.test.ts` fail on my machine. They
passed in CI on the previous head, and this PR does not touch that code.
A compute logs test failed once and passes when run alone.
- `oxfmt`, `oxlint`, `tsc` and `knip` are clean. A frozen `pnpm install`
passes.

## 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] Relevant package tests pass for every touched workspace, and the
touched TypeScript workspace type-checks. Locally, `lint:check`,
`fmt:check` and `knip:check` pass. `lint:actions:check` did not run,
because `jactionlint` is not installed, and this PR changes no workflow.

## Why now

supabase-swift v3 launches as Public Alpha on 2026-12-11. Its demo flow
is `supabase gen types --lang swift`. This PR must ship in a CLI release
before that date.

<!-- ci retrigger -->

---------

Co-authored-by: Andrew Valleteau <avallete@users.noreply.github.com>
Co-authored-by: avallete <8771783+avallete@users.noreply.github.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
This bumps storage from v1.96.0-r0 to v1.96.2-r0.


https://github.com/supabase/slim-services/releases/tag/storage-v1.96.2-r0

Planned after supabase/slim-services published v1.96.2-r0. A newer
relevant release rewrites this branch from develop and replays any
commits others pushed to it.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@supabase-cli-releaser supabase-cli-releaser Bot added the do not merge Approve to apply; do not merge. label Nov 17, 2026
@supabase-cli-releaser
supabase-cli-releaser Bot requested a review from a team as a code owner November 17, 2026 02:16
supabase-cli-releaser Bot and others added 6 commits November 17, 2026 02:36
This bumps realtime from v2.167.0-r0 to v2.168.0-r0.


https://github.com/supabase/slim-services/releases/tag/realtime-v2.168.0-r0

Planned after supabase/slim-services published v2.168.0-r0. A newer
relevant release rewrites this branch from develop and replays any
commits others pushed to it.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
`functions deploy`, `projects create` and `bootstrap` call the
Management API with `executeRaw` and build their own status errors, so a
plan-gate denial (`entitlement_required`) reached the user without the
upgrade hint, the JSON `error.entitlement` or the
`cli_upgrade_suggested` event that `mapHttpError` callers already get. I
moved the envelope read into one shared function,
`planGateFromResponse`, and both paths now use it.

**Changed:**
- **Plan-gated project create**: I made `projects create` and
`bootstrap` (which shares the create step) handle a 4xx that carries the
envelope: each prints the upgrade hint once, adds `entitlement` to the
JSON error, fires `cli_upgrade_suggested` and classifies the error as
`plan_limit`.
- **Plan-gated function deploy**: I applied the same handling to
function create, update, API deploy and bulk update.
- **`mapHttpError`**: I switched it to read the envelope from the body
text it already holds, through the same shared function. Its behavior is
unchanged.

**Note:** a `--use-api` deploy of several functions still reports its
failures as one aggregate error with no entitlement. I left that path
for a follow-up.

## Linear
- fixes GROWTH-1484
The gateway CORS live test intermittently failed on the live job in two
ways, both from a brief 403 on the freshly created staging project:

- Staging answered the two \`OPTIONS /rest/v1/\` probes with a bare 403
and no CORS headers, so the stack-versus-staging comparison failed.
- \`functions deploy\` got a 403 from the Management API's
list-functions call.

The staging readiness gate now also waits for both REST preflight probes
to stop answering 403 before staging is recorded, and \`functions
deploy\` is retried (5s apart, up to 12 times) when it fails with a 403.
Other deploy failures still fail immediately, and the
stack-versus-staging assertion is unchanged.

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

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
This bumps postgrest from v16.5-r0 to v16.6-r0.


https://github.com/supabase/slim-services/releases/tag/postgrest-v16.6-r0

Planned after supabase/slim-services published v16.6-r0. A newer
relevant release rewrites this branch from develop and replays any
commits others pushed to it.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
## TL;DR
The routed-peer plain probe now ignores SIGPIPE, so it reports the
proxy's close instead of dying.

- `HttpProxy.integration.test.ts › gives a routed peer inside the bridge
network no plain byte, but TLS`: the namespace `bash` probe failed with
`Process interrupted due to receipt of signal: 'SIGPIPE'`. The proxy
closes a plain connection from a non-loopback peer. When that close
arrives before `printf >&3` writes the request, bash dies of SIGPIPE,
and the `&&` chain never reaches the read. The probe now uses the
api.tls probe pattern from #7590: `trap '' PIPE`, a write that can fail
without stopping the chain, and the read that reports the close.

## ref
spotted in:
https://github.com/supabase/cli/actions/runs/43972802044/job/133669050994

---
_Generated by [Claude
Code](https://claude.ai/code/session_01MBEk1LoYxzbfzYDtuz4z4F)_

Co-authored-by: Claude <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>
supabase-cli-releaser Bot and others added 4 commits November 17, 2026 10:33
This bumps storage from v1.96.2-r0 to v1.96.3-r0.


https://github.com/supabase/slim-services/releases/tag/storage-v1.96.3-r0

Planned after supabase/slim-services published v1.96.3-r0. A newer
relevant release rewrites this branch from develop and replays any
commits others pushed to it.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This bumps realtime from v2.168.0-r0 to v2.170.0-r0.


https://github.com/supabase/slim-services/releases/tag/realtime-v2.170.0-r0

Planned after supabase/slim-services published v2.169.0-r0. A newer
relevant release rewrites this branch from develop and replays any
commits others pushed to it.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This bumps storage from v1.96.3-r0 to v1.96.4-r0.


https://github.com/supabase/slim-services/releases/tag/storage-v1.96.4-r0

Planned after supabase/slim-services published v1.96.4-r0. A newer
relevant release rewrites this branch from develop and replays any
commits others pushed to it.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
## Summary

The published config schema
(`https://supabase.com/schemas/config/v1.json`) sets
`additionalProperties: false` at the root but never declared `$schema`.
VS Code's JSON validator doesn't exempt `$schema`, so a `config.json` or
`config.jsonc` that points at our schema shows `Property $schema is not
allowed.` on that line. The same applies to a top-level `$schema` key in
TOML for editors that read the schema. The CLI itself already accepts
the key; only the editor schema rejected it.

This declares `$schema` as the first root property: an optional string
with the hosted URL in `examples`. `examples` still gives completions in
VS Code and a hint to agents reading the schema, without rejecting other
values such as a local copy or a `node_modules` path. `CliConfigSchema`
is unchanged, so `$schema` doesn't become a decoded config field.

- `toCliConfigJsonSchema()` adds the property
- `apps/cli/schemas/config/v1.json` is regenerated with `pnpm build`
(config) and `pnpm schemas:generate` (cli). The diff is only the new
property; project-config and lock outputs are unchanged
- A new unit test checks the property shape, that it isn't required, and
validates a document with `$schema` against the published schema via the
existing Ajv helper

The lock schema's `$schema` handling is discussed separately in
CLI-3145.

## Linked issue

No issue; found while discussing CLI-3145.

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

## Checklist

- [x] The PR title follows [Conventional
Commits](https://www.conventionalcommits.org/) (e.g. `fix(cli): …`).
- [x] Tests added or updated for the change.
- [x] From the repository root, `pnpm check:all` passes; relevant
package tests pass for every touched workspace, and `pnpm types:check`
passes for each touched TypeScript workspace (or workspace declaring
it).
supabase-cli-releaser Bot and others added 11 commits November 17, 2026 12:37
This bumps pgmeta from v0.100.0-r0 to v0.100.1-r0.


https://github.com/supabase/slim-services/releases/tag/pgmeta-v0.100.1-r0

Planned after supabase/slim-services published v0.100.1-r0. A newer
relevant release rewrites this branch from develop and replays any
commits others pushed to it.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
… release (#7666)

## What

Moves the `supabase/setup-cli` smoke test out of the release pipeline
and into a daily scheduled workflow.

## Why

The post-release smoke test installed through setup-cli seconds after
the npm publish, while the registry could still serve an older package
list. npm then skipped the new `@supabase/cli-<platform>` optional
dependency without failing, the npm shim could not find a binary, and
setup-cli fell back to the GitHub release. Slack reported this as a
setup-cli npm fallback on most releases, although it was only
propagation delay and the release itself was fine.

## How

- `setup-cli-smoke-test.yml` runs daily. It resolves the newest version
on each npm dist-tag that ships the `@supabase/cli-*` platform packages
(`latest`, `beta`, `next`, `v<N>.stable`) and skips versions published
less than an hour earlier. Each version runs the existing setup-cli
v1/v2/v3 matrix on Linux, macOS, Windows and Alpine, plus the forced
GitHub release fallback job.
- Scheduled runs post to Slack when a job fails or when setup-cli v3
falls back from npm. `workflow_dispatch` with a `version` tests one
release without posting.
- The release pipeline no longer calls the smoke test: the
`setup-cli-smoke` job, its fallback output, and the separate fallback
Slack notice are removed, along with the fallback notice on success
messages.
- `wait-for-npm-version.sh` is removed, since tested versions are
already an hour old.
- The release process doc describes the daily check.

`v2.x` still runs the post-release smoke test from its own copy of the
release pipeline; a backport that removes the `setup-cli-smoke` job
there stops the same alerts on maintenance releases.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
## TL;DR
Owner integration tests that start real services ran on the virtual
`TestClock`, so any retry in their path could hang until the test
timeout.

- `Owner.integration.test.ts › credential lookup leaves a fresh stack
untouched for custom database credentials`: hung until its 30s timeout
once, green on rerun of the same SHA. The test ran under `it.effect`,
whose `TestClock` never advances, while the database readiness probe
(`Database.ts`) and the lock and port-reservation acquisitions retry on
`Schedule.spaced`. When the first probe or lock attempt failed, the
retry waited forever. The tests in this file that do real owner, SQLite,
file and process I/O now run under `it.live`, like their siblings. No
test in the file relies on virtual time.

## ref
spotted in:
-
https://github.com/supabase/cli/actions/runs/42807806171/job/129801375563
(failing)
-
https://github.com/supabase/cli/actions/runs/42807806171/job/129803236031
(green rerun)

---
_Generated by [Claude
Code](https://claude.ai/code/session_01MBEk1Pf3phzjWscZfmvHZY)_

Co-authored-by: Claude <noreply@anthropic.com>
This bumps storage from v1.96.4-r0 to v1.97.0-r0.


https://github.com/supabase/slim-services/releases/tag/storage-v1.97.0-r0

Planned after supabase/slim-services published v1.97.0-r0. A newer
relevant release rewrites this branch from develop and replays any
commits others pushed to it.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
## Summary

Extend the existing AI review with advisory feedback on changed CLI
reference prose, using the Supabase docs team’s current style guide
rather than the retired prose linter.

A trusted preparation job resolves one upstream revision and supplies
the same readable guidance snapshot to both reviewers and adjudication.
Findings must quote changed prose and cite a rule at that revision.
Retrieval and delivery failures are reported without blocking ordinary
code review or claiming a style pass.

A local CLI reference skill shares the review procedure without copying
upstream style rules. Existing review authorization and trigger behavior
remain unchanged.

Closes
[CLI-2681](https://linear.app/supabase/issue/CLI-2681/apply-upstream-docs-guidance-in-cli-reference-ai-review).
## Summary

Validate the generated CLI reference before writing a local preview or
starting Git operations for the docs-site PR. The publisher now checks
nested document fields and compares command IDs and subcommand links
against the documented command tree, replacing the fixed command-count
threshold.

Missing, duplicate, unexpected, or malformed entries stop publishing
with an error. Unlisted and explicitly excluded commands remain outside
the reference.

Closes
[CLI-2680](https://linear.app/supabase/issue/CLI-2680/validate-generated-files-before-pushing).
<!--
Before opening this PR, confirm the linked issue is open and carries the
`open-for-contribution` label. PRs from external contributors that don't
follow
the workflow in CONTRIBUTING.md are closed automatically.
@supabase members working from Linear tickets are exempt.
-->

## Summary

addresses a few `mise` housekeeping tasks that i noticed when running
`mise install`:
- [x] updates to the recommended backend for `jactionlint` installations
- [x] upgrades our `mise.lock` lockfile version
- [x] updates our `mise` `min_version` and our `mise` version in CI

## Checklist

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


https://github.com/supabase/slim-services/releases/tag/realtime-v2.171.0-r0

Planned after supabase/slim-services published v2.171.0-r0. A newer
relevant release rewrites this branch from develop and replays any
commits others pushed to it.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.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>
## Summary

Switches the Codex side of the AI review from `gpt-6.1-sol` to
`gpt-6.2-sol`.

- `.github/ai-models.json`: `codex.sol` is now `gpt-6.2-sol`
- `ai-review.yml`: Codex CLI pin goes from 0.159.2 to 0.169.1, the first
stable release whose model catalog carries `gpt-6.2-sol` (0.169.0
doesn't have it)

The codex-action v1.11 pin and its Dependabot ignore are untouched.
`codex-rs/exec/src/cli.rs` only gained flags between 0.159.2 and
0.169.1, so everything the action passes still parses.

`effort: high` stays explicit - 6.2-sol's catalog default is `low`. Its
default context window is 500k (max 872k), so very large diffs have less
headroom than before.

This hasn't run against a real PR yet. I'd like a `workflow_dispatch`
run on one before we trust it on the automatic path, which also confirms
our `OPENAI_API_KEY` has access to the model.

## Linked issue

N/A

- [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.
- [x] From the repository root, `pnpm check:all` passes; relevant
package tests pass for every touched workspace, and `pnpm types:check`
passes for each touched TypeScript workspace (or workspace declaring
it).
This bumps realtime from v2.171.0-r0 to v2.172.0-r0.


https://github.com/supabase/slim-services/releases/tag/realtime-v2.172.0-r0

Planned after supabase/slim-services published v2.171.1-r0. A newer
relevant release rewrites this branch from develop and replays any
commits others pushed to it.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

This branch was successfully deployed

1 active (outdated) and 1 inactive (outdated) deployments
config-release — 0f27780a Deployed Nov 17, 2026 by github-merge-queue[bot] via Publish #61
auto-approve — 3f7eae0d Deployed Nov 17, 2026 by supabase-cli-releaser[bot] via Approve the reviewed sync #10976
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge Approve to apply; do not merge.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants