Skip to content

fix: fail API startup when migration fails - #132

Merged
QThans merged 1 commit into
mainfrom
dev
Sep 24, 2026
Merged

QThans merged 1 commit into
mainfrom
dev

Conversation

@QThans

@QThans QThans commented Sep 24, 2026

Copy link
Copy Markdown
Collaborator

Fix

  • Close the PostgreSQL jsonb_set call in the 1.0.3 template migration.
  • Write the startup migration marker only after migrations succeed, so a failed migration cannot be skipped on container restart.

Evidence

  • Production API logs showed PostgreSQL syntax error near WHERE; Coolify still marked the deployment healthy after restart, while Store stayed at template 1.0.2.
  • Shell syntax check passes and the corrected SQL literal/call is balanced.

After deployment, verify the migration-completed log, Store version 1.0.3, then run real profile/post/Reel E2E.

@vercel

vercel Bot commented Sep 24, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
anycrawl-docs Blocked Blocked Sep 24, 2026 11:24am UTC

@QThans
QThans merged commit 8bbecc6 into main Sep 24, 2026
5 of 6 checks passed

This branch had an error being deployed

1 failed deployment
Preview — 25f7c82b Deployed Sep 24, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant