chore: sync API types from infrastructure - #5897
Merged
Merged
Conversation
supabase-oss
approved these changes
Jul 17, 2026
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9f1a1e9aa9
ℹ️ 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".
supabase-oss
approved these changes
Jul 17, 2026
supabase-cli-releaser
Bot
force-pushed
the
sync/api-types
branch
from
July 19, 2026 14:37
9f1a1e9 to
c700a1b
Compare
supabase-oss
approved these changes
Jul 19, 2026
supabase-oss
approved these changes
Jul 20, 2026
supabase-oss
approved these changes
Jul 20, 2026
supabase-oss
approved these changes
Jul 20, 2026
supabase-oss
approved these changes
Jul 20, 2026
supabase-oss
approved these changes
Jul 20, 2026
supabase-oss
approved these changes
Jul 20, 2026
supabase-oss
approved these changes
Jul 20, 2026
supabase-oss
approved these changes
Jul 20, 2026
supabase-oss
approved these changes
Jul 20, 2026
supabase-oss
approved these changes
Jul 20, 2026
supabase-oss
approved these changes
Jul 20, 2026
supabase-oss
approved these changes
Jul 20, 2026
supabase-oss
approved these changes
Jul 20, 2026
supabase-oss
approved these changes
Jul 20, 2026
supabase-oss
approved these changes
Jul 20, 2026
supabase-oss
approved these changes
Jul 20, 2026
Contributor
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase/cli/supabase@4c88ac46b9cfa37a1e70d54200726571028cc081Preview package for commit |
supabase-cli-releaser
Bot
force-pushed
the
sync/api-types
branch
from
July 20, 2026 17:26
15c551c to
be65b73
Compare
supabase-oss
approved these changes
Jul 20, 2026
This comment has been minimized.
This comment has been minimized.
supabase-cli-releaser
Bot
force-pushed
the
sync/api-types
branch
from
July 20, 2026 22:08
be65b73 to
96b3260
Compare
supabase-oss
approved these changes
Jul 20, 2026
supabase-oss
approved these changes
Jul 21, 2026
supabase-oss
approved these changes
Jul 21, 2026
supabase-oss
approved these changes
Jul 21, 2026
supabase-oss
approved these changes
Jul 21, 2026
supabase-oss
approved these changes
Jul 21, 2026
supabase-cli-releaser
Bot
force-pushed
the
sync/api-types
branch
from
July 21, 2026 10:01
96b3260 to
f790cb8
Compare
supabase-oss
approved these changes
Jul 21, 2026
supabase-cli-releaser
Bot
force-pushed
the
sync/api-types
branch
from
July 21, 2026 10:39
f790cb8 to
de39196
Compare
supabase-oss
approved these changes
Jul 21, 2026
supabase-oss
approved these changes
Jul 21, 2026
supabase-oss
approved these changes
Jul 21, 2026
supabase-oss
approved these changes
Jul 21, 2026
supabase-oss
approved these changes
Jul 21, 2026
supabase-oss
approved these changes
Jul 21, 2026
avallete
approved these changes
Jul 21, 2026
pull Bot
pushed a commit
to oogalieboogalie/cli
that referenced
this pull request
Aug 5, 2026
## TL;DR `supabase sso list` dies with `SchemaError(Missing key at ["items"][0]["domains"][0]["id"])` The platform dropped `id` from `saml` and `domains[]` on the sso provider responses on Jul 21. Go absorbed it same day in supabase#5897 we didn't, since our `openapi.json` still marks `domains[].id` required and we decode strictly. `show` and `update`'s preflight hit the same field, `remove` hits `saml.id` one earlier they surface one at a time because decoding stops at the first missing key, which is why it reads like a regression of supabase#5475. The snapshot never healed because that same spec change tripped the two `saml/required` `test` ops in `openapi-overrides.json`, the first sync run after the change, and **api-package-sync has been red every run since** so this unblocks that too. The two overrides go with it: upstream adopted both, there's nothing left to relax, and keeping them only re-arms the same hard stop next time. Resynced the five schemas from the live spec and regenerated byte-identical to a fresh `pnpm generate`, so the next sync won't fight it. Nothing read the dropped fields, and `sso.go-payload.ts` already mirrored Go's struct without them, so `-o yaml|toml` is unchanged and `-o json` now drops them the way Go does, even if a project still echoes them. Two things the resync pulled in that are worth naming rather than leaving for a reviewer to spot.... the `attribute_mapping…default` union flipped `oneOf` → `anyOf` upstream, so the generated `Schema.Union` loses `{ mode: "oneOf" }` — inert here, the four branches are disjoint so no value can match two. And the fixture churn: the sso suites were feeding themselves `saml.id`/`domains[].id` that the API doesn't send, so they'd have stayed green however stale the schema got. They use the real payload shape now.... ## refs - closes supabase#6051 - supabase#5897 (the same ten fields removed on the Go side)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.