Skip to content

chore: sync API types from infrastructure - #5713

Merged
avallete merged 2 commits into
developfrom
sync/api-types
Jun 30, 2026
Merged

chore: sync API types from infrastructure#5713
avallete merged 2 commits into
developfrom
sync/api-types

Conversation

@supabase-cli-releaser

Copy link
Copy Markdown
Contributor

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.

@blacksmith-sh

This comment has been minimized.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0d82531ff8

ℹ️ 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".

Comment thread apps/cli-go/pkg/api/types.gen.go
@avallete

Copy link
Copy Markdown
Member

@copilot Let's fix this

Copilot AI commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

@copilot Let's fix this

I've updated storage.go to include the PurgeCache field that was added in the latest API generation but missing from the storage config struct. This should fix the compilation error in the tests.

Commit: b96a785

auto-merge was automatically disabled June 26, 2026 16:13

Head branch was pushed to by a user without write access

Copilot AI requested a review from a team as a code owner June 26, 2026 16:13
Copilot AI requested a review from avallete June 26, 2026 16:13
@avallete
avallete enabled auto-merge June 26, 2026 16:30
@github-actions

github-actions Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Supabase CLI preview

npx --yes https://pkg.pr.new/supabase/cli/supabase@274ee4e390b140cccd8b72216c058df569abb9c0

Preview package for commit 274ee4e.

@blacksmith-sh

This comment has been minimized.

@supabase-cli-releaser
supabase-cli-releaser Bot force-pushed the sync/api-types branch 7 times, most recently from b0a0829 to 3c2129c Compare June 30, 2026 02:25
@blacksmith-sh

This comment has been minimized.

…5737)

Add support for new storage and PostgreSQL configuration features in the
Go CLI API types and storage configuration.

**Changes:**

- **Feature entitlements**: Added two new feature keys to
`V1ListEntitlementsResponseEntitlementsFeatureKey`:
  - `api.members.roles` — API members roles management
  - `storage.purge_cache` — Storage cache purging capability

- **PostgreSQL configuration**: Extended
`PostgrestConfigWithJWTSecretResponse`, `V1PostgrestConfigResponse`, and
`V1UpdatePostgrestConfigBody` types with:
- `DbPoolAcquisitionTimeout` field for configuring database pool
acquisition timeout (defaults to 10 when null)
  - Improved field alignment and documentation

- **Storage configuration**: Added `PurgeCache` feature toggle to:
  - `StorageConfigResponse` — read-only storage configuration response
  - `UpdateStorageConfigBody` — storage configuration update request

These changes enable clients to manage cache purging and fine-tune
PostgreSQL connection pool behavior through the Management API.

https://claude.ai/code/session_01HCAM37nBUbzHa4u7gr9876

---------

Co-authored-by: supabase-cli-releaser[bot] <246109035+supabase-cli-releaser[bot]@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>
@avallete
avallete added this pull request to the merge queue Jun 30, 2026
Merged via the queue into develop with commit fc6dd9c Jun 30, 2026
21 of 22 checks passed
@avallete
avallete deleted the sync/api-types branch June 30, 2026 08:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants