fix(supabase): sync local migrations with remote history (asset registry) - #84
Merged
Conversation
…026-06-29 The Supabase migration check on main fails with 'Remote migration versions not found in local migrations directory': versions 20260629193917 (asset_registry_v1) and 20260629194328 (asset_registry_rls) exist in supabase_migrations.schema_migrations on the remote (applied via MCP apply_migration during the asset-registry work) but were never committed. Reconstructs both files verbatim from the statements stored in the remote migration history so local and remote histories match. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Updates to Preview Branch (fix/supabase-migration-sync) ↗︎
Tasks are run on every commit but only new migration files are pushed.
❌ Branch Error • Wed, 15 Jul 2026 19:48:40 UTC View logs for this Workflow Run ↗︎. |
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.
Fixes the failing Supabase migration check on
main(commit 5b8a370): Remote migration versions not found in local migrations directory.Root cause
Versions
20260629193917(asset_registry_v1) and20260629194328(asset_registry_rls) were applied to the remote database on 2026-06-29 via MCPapply_migrationduring the asset-registry work, but the corresponding files were never committed — so the remote history has two versions the repo doesn't know about.Fix
Reconstructs both migration files verbatim from
supabase_migrations.schema_migrations.statementson the remote, with matching timestamps. No schema changes — the SQL is already applied; this only makes local history match remote.Note for
feat/asset-registry-docs-v1That branch carries
20260629120000_asset_registry.sqlwith overlapping content but a different (earlier) timestamp that the remote has never applied. When that branch is rebased on this, the file should be dropped in favor of the two files added here — otherwisedb pushwill try to apply it again.🤖 Generated with Claude Code