Repository navigation
chore(repo): sync develop into next - #7245
Conversation
This adds postgres 17.11.0.006-orioledb-r0 as a new release line. https://github.com/supabase/slim-services/releases/tag/postgres-17.11.0.006-orioledb-r0 Planned after supabase/slim-services published 15.19.0.006-r0. This branch is rewritten from develop whenever a newer relevant release arrives. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This bumps postgres from 15.19.0.005-r0 to 15.19.0.006-r0. https://github.com/supabase/slim-services/releases/tag/postgres-15.19.0.006-r0 Planned after supabase/slim-services published 15.19.0.006-r0. This branch is rewritten from develop whenever a newer relevant release arrives. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This bumps postgres from 17.11.0.005-r0 to 17.11.0.006-r0. https://github.com/supabase/slim-services/releases/tag/postgres-17.11.0.006-r0 Planned after supabase/slim-services published 15.19.0.006-r0. This branch is rewritten from develop whenever a newer relevant release arrives. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…2749) (#7216) ## TL;DR stack `rest` now comes up even when a `db_pre_request` hook rejects requests without an app header. ## whats missing? the stack never started PostgREST's admin server, so it checked readiness with a plain `GET /`. that request goes through the project's `db_pre_request` hook, which answers 403 to anything without the header, so rest never looked ready. eager start timed out, and lazy start gave the first API request a 502 after a min ## now fixed by: rest now runs the admin server and checks its `/ready` same as legacy start, so the hook never sees the probe. recipes pick the probed port with a new optional `healthPort`, which defaults to `http` <details> <summary>visual rep:</summary> ```mermaid flowchart TB subgraph before direction LR A1["readiness probe"] -->|"GET /"| B1["data port"] B1 --> C1["db_pre_request hook"] C1 -->|"403"| D1["never ready (eager timeout, lazy 502)"] end subgraph after direction LR A2["readiness probe"] -->|"GET /ready"| B2["admin server"] B2 -->|"200 once the schema cache loads"| D2["ready"] end before ~~~ after ``` </details> ## ref: - closes: #7215
# Conflicts: # apps/cli-go/pkg/config/templates/Dockerfile
Claude resolved the merge of
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Superseded by a newer AI review
🤖 AI Review
Both independent reviews completed with no findings. Verification of the sync resolution confirms that the deleted Go Dockerfile is byte-identical to the retained TypeScript Dockerfile, whose PostgreSQL tags match the artifact catalog. The generator targets the retained file, and no executable references to the deleted path were found. No merge-introduced issues identified.
Findings
No issues found.
Stats
Claude findings: 0 · Codex findings: 0 · Confirmed: 0 · Refuted: 0 · Uncertain: 0
Models: claude-opus-5-5 + gpt-6.1-sol · Trigger: manual · Workflow run
This review runs once per PR. A maintainer can request another with a /ai-review comment.
Claude repair roundThe integration tests failed because 0 findings fixed, 0 declined (workflow run). |
|
The repair commit moved the head to |
There was a problem hiding this comment.
🤖 AI Review
Both independent reviews completed with zero findings. My inspection found no additional sync-specific issues: the obsolete Go Dockerfile remains deleted, its retained TypeScript counterpart preserves the image definitions, and all six fixture updates match PostgreSQL 17.11.0.006 in the Dockerfile and artifact catalog.
Findings
No issues found.
Stats
Claude findings: 0 · Codex findings: 0 · Confirmed: 0 · Refuted: 0 · Uncertain: 0
Models: claude-opus-5-5 + gpt-6.1-sol · Trigger: manual · Workflow run
This review runs once per PR. A maintainer can request another with a /ai-review comment.
supabase-oss
left a comment
supabase-oss
left a comment
There was a problem hiding this comment.
CI is green and the AI review raised nothing the merge introduced, so this approves Claude's resolution of the sync (https://github.com/supabase/cli/actions/runs/39316086839).
Merging
developintonextconflicts. This branch starts at the tip ofdevelop(600ca9a);nextis at76fc6bb.Conflicting files:
apps/cli-go/pkg/config/templates/DockerfileTo resolve:
git fetch origin git switch sync/develop-into-next git merge origin/next # resolve the conflicts, then commit git push origin sync/develop-into-nextApprove to fast-forward
next; do not use the merge button.