chore: sync API types from infrastructure - #6417
Merged
Merged
Conversation
supabase-oss
approved these changes
Sep 1, 2026
supabase-oss
approved these changes
Sep 1, 2026
Contributor
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase/cli/supabase@6cc874b920ecaba08af551d291733a9c10dfd759Preview package for commit |
pull Bot
pushed a commit
to chizee/cli
that referenced
this pull request
Sep 1, 2026
…hema (supabase#6425) ## What kind of change does this PR introduce? Bug fix (CI). ## What is the current behavior? The `Codegen` job in the `CI` workflow runs `go generate` against the live Management API spec (`api.supabase.green`) and fails the build if the checked-in `pkg/api` files drift from what it produces. Upstream started splitting every response component schema into a base and `_Output` variant (e.g. `JitListAccessResponse` -> `JitListAccessResponse_Output`), which broke three `apps/cli-go/api/overlay.yaml` selectors targeting the old schema name: ``` failed to apply Overlay "api/overlay.yaml" ... selector "$.components.schemas.JitListAccessResponse.properties.items.items.anyOf[0].properties.invite_id" did not match any targets ``` This has failed the `Codegen` check on every `develop` commit since supabase#6417 (merged 2026-09-01), blocking the merge queue for all PRs since the `merge_group` trigger has no path filter. ## What is the new behavior? - `overlay.yaml` selectors repointed at `JitListAccessResponse_Output` (schema shape is unchanged, only the name). - Regenerated `pkg/api/{types,client}.gen.go` against the current live spec, which also renames every other response schema type to its `*Output` counterpart. - Renamed all downstream Go references (`pkg/config`, `pkg/function`, `internal/utils`, `internal/telemetry`, `internal/functions/download`) to the new `*Output` type names so the module still builds. Verified: `go build ./...`, `go vet ./...`, `golangci-lint run`, and `go generate` (re-run to confirm idempotency) all pass in `apps/cli-go`. `go test ./...` in `apps/cli-go` is green aside from two pre-existing, environment-only failures (no local Docker daemon). `pkg/config`'s test suite has ~20 pre-existing failures that are identical on a clean `develop` checkout (confirmed via a baseline worktree) — unrelated to this change, and that submodule isn't part of the CI `Test` job's scope anyway. ## Related Issue(s) Unblocks the merge queue (e.g. supabase#6423).
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
1 participant
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.