Repository navigation
Restore recorded migration source identities - #125
Draft
sidneyswift wants to merge 3 commits into
Draft
sidneyswift wants to merge 3 commits into
sidneyswift wants to merge 3 commits into
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
|
Updates to Preview Branch (codex/migration-history-repair) ↗︎
Tasks are run on every commit but only new migration files are pushed.
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
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.
Current release hold — refreshed November 17, 2026. The October 26 single-pending-migration observation below is historical. This PR at
3f2c84903286f0c950faa03bd2cef72f20d5d8adcomposes without conflicts with current main7708e337feca212563bdfa48934a72227bcf1b63, but fresh configured-target metadata now shows four pending versions after history alignment:20261022120000_context_catalog_cases,20261106120000_email_send_log_reason,20261110010000_ingestion_catalog, and20261110010100_ingestion_catalog_page_budget. A catalog-only apply decision is insufficient for a main-merge integration that could apply all four. Keep draft/unmerged until the actual release bundle is qualified and explicitly approved, or a supported non-applying review-only route is proven. No integration/history override is authorized.The unchanged catalog SQL passed its two existing disposable transaction tests on PostgreSQL 15 and 17 against the offline combined source tree. This does not qualify the other three pending migrations, full history replay, production execution or intended-actor acceptance. No source change was needed.
Original October 26 qualification (historical)
Supabase history checks fail because eight recorded migration versions are absent locally. Restore six original evidence migration files and rename release-pack jobs and professional artist accounts to their recorded timestamps. Every SQL file is byte-identical to both its preserved Git source and the recorded applied statement; fixture/document references follow the two renames.
MERGE HOLD — explicit migration approval required. After alignment, the sole pending migration is
20261022120000_context_catalog_cases.sql(unchanged, from #120). Fixing history can let the main-merge Supabase integration apply it. This PR does not authorize that apply. Keep draft until explicit approval or a proven non-applying review-only path; do not alter integration settings or repair remote history to bypass the hold.Validation: all eight SQL byte comparisons match; 276 recorded remote versions versus 277 unique local versions; zero remote-only versions; only catalog cases remains local-only. Python fixture syntax and diff checks pass. Independent Spec and Standards reviews found no actionable issues. No remote SQL apply, history repair, grants, runtime changes, or test replay was performed.
tests/MIGRATION-HISTORY.mdrecords source identities, hashes, limitations, and the pending-apply boundary. PR #90 remains separate historical provenance; this PR does not close it or claim its entire feature acceptance. Other environments with different recorded history require separate review.Catalog size follow-up location
The temporary size correction3b86a64 was restored through normal revertd657a92; current source tree is identical to original3f2c849. No reset, force push, migration apply or deployment occurred. The size correction is being prepared separately as an inactive proposal outside migrations; this draft PR retains its original source and release gates.