Repository navigation
[Tracking] Repository review 2026-10-14 fixes #479
Description
Summary
This tracker holds the fixes from the repository review of 2026-10-14. Each child issue fixes one defect that was checked against the code. The review itself is not public. Only part of it was available, so this list covers the findings that were checked. The docs and README review of the same day is tracked in #487.
Child issues, in priority order
| Priority | Issue | Why |
|---|---|---|
| 1 | #475 | The auto-rollback starts the failed build again. Measured. |
| 2 | #476 | make clean tears down the production stack and deletes its volumes. |
| 3 | #477 | The 50 editor Cypress specs run in no CI job. |
| 4 | #478 | A pad render error offers no Reload and no component stack. Follow-up to #436. |
| 5 | #488 | The error page calls every client render error a server 404. From the staff review of #478. |
Already tracked
The review also found that production grants have drifted from git. These issues already cover that work:
- Add a read-only grant guard to run after each
db push#317 add a read-only grant guard to run after eachdb push - Remove prod-only drift: four functions and the
PushSentLogtable #320 remove prod-only drift: four functions and thePushSentLogtable - Revoke PUBLIC and anon EXECUTE on internal schema helpers #469 revoke PUBLIC and anon EXECUTE on internal schema helpers
- Remove anon default table privileges on production #470 remove anon default table privileges on production
- [Tracking] Supabase prod security and performance review, 2026-09-28 #327 tracks the Supabase prod security and performance review
Not filed, and why
- Two error shapes in the HTTP API. This was decided.
envelope.tsowns the house envelope, and link-metadata keeps its own shape on purpose. - A breaking change in a minor release, and an untyped WebSocket protocol. The review named no change and no defect. File each one if someone finds a concrete case.
- A single host with manual backups. Supabase takes the database backups.
docs/self-hosting/README.mddocuments the other three stores. A second host is a cost decision, not a defect. stage.docs.plus.ymlnever runs on a push. This is known, and AGENTS.md records it. Staging is used throughworkflow_dispatch, as Require a password on production Redis #438 plans.
Open decision
- Should the RLS policies get pgTAP tests? Recommended: do not build a general suite. No test covers the RLS policies today. When an RLS policy bug ships, pin that one policy with a
supabase test dbtest in the same fix.
Generated by Claude Code
Activity