ci: allow db:migrate to fail without blocking deploy#84
Open
ncrmro wants to merge 1 commit into
Open
Conversation
The Turso DB still has the legacy Next.js schema, so drizzle-kit migrate errors when applying our bundled SQL migrations (tables already exist with no drizzle metadata table). Today the DB is inert scaffolding — no runtime client reads it — so a failed migration shouldn't block the worker deploy. The latest post-merge Deploy run failed exactly here. Add `continue-on-error: true` to the migration step. The workflow still runs the migration so the wiring stays warm; if/when the DB is revived for real, drop this flag and reconcile the schema first. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
ncrmro-website | 0675d7e | May 16 2026, 01:36 PM |
4 tasks
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
The post-merge Deploy run for #82/#83 failed at `bun run db:migrate`. The DB still has the legacy Next.js schema (tables exist without drizzle's bookkeeping table), so applying our bundled migrations errors out. Today nothing in the runtime reads the DB — it's pure scaffolding — so a failed migration shouldn't block the worker deploy.
Adds `continue-on-error: true` to the migration step. When/if the DB is revived for real, drop the flag and reconcile the schema first.
Test plan
🤖 Generated with Claude Code