chore: sync API types from infrastructure#5697
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8bc6549b7b
ℹ️ 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".
| return nil, err | ||
| } | ||
|
|
||
| operationPath := fmt.Sprintf("/v1/projects/%s/analytics/endpoints/logs", pathParam0) |
There was a problem hiding this comment.
Keep the existing log helper on logs.all
For callers that already use V1GetProjectLogs/V1GetProjectLogsWithResponse, this silently switches the request from the current logs endpoint to /logs. The released Management API still documents project log queries at /v1/projects/{ref}/analytics/endpoints/logs.all (docs), and the repo's TS generated contract still maps v1GetProjectLogs to logs.all, so clients pointed at api.supabase.com can start getting 404/failed log queries unless the existing method remains on logs.all or all callers are migrated to the new V1GetProjectLogsAll method.
Useful? React with 👍 / 👎.
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase/cli/supabase@8bc6549b7b6e57e8d7216e0828593b3d8e3b7016Preview package for commit |
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.