Rewrite the Supabase pending-work plan for the current state - #178
Merged
Merged
Conversation
Tasks 1 and 2 are done and every repo migration is applied. Record how the manual applies were done, and what is still open: the migration history re-key, deploying newsletter-subscribe, and making the preview check required. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Summary
dev-plans/supabase-pending-work-2026-08.mdstill listed work that was finished on 2026-09-16. This PR rewrites it around the current production state.Current state. Every repo migration is applied to production, and
report-client-erroris deployed.20260816000000(client_error_log),20260915000000(workspaces) and20260916000000(profiles) were applied by hand, each recorded under its repo version.How to apply by hand. The procedure used for those three migrations until sync works again:
It also explains why the connector's
apply_migrationshould not be used for repo files.Open tasks.
Supabase Previewonmainstill fails with Remote migration versions not found. The doc includes:user_app_documents*is used bysrc/shared/user-data; thefocus_*records belong to Focus-Planner);migration repaircommands.newsletter-subscribeis not deployed, although the site calls it. The doc lists the requiredRESEND_API_KEY.Supabase Previewrequired oncemainis green. The doc also notes the stale-preview-branch pitfall seen on Add shared workspaces for small teams #175.trim_calculation_history()execute grants;Also
.gitignore: ignore every.envfile (.env,.env.*, e.g.supabase/functions/.env), not only the*.localvariants;.env.examplestays allowed. A repo-wide secret scan (tracked files and full history) found nothing but the public anon key, which ships in the site bundle by design.🤖 Generated with Claude Code