Merged
Conversation
Co-authored-by: Kent C. Dodds <me+github@kentcdodds.com>
|
Cursor Agent can help with this pull request. Just |
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.
Test Plan
Checklist
Screenshots
Note
Low Risk
Single config change to the startup migration command; low blast radius, with the main risk being an incorrect Prisma binary path causing migrations to fail on deploy.
Overview
Updates Fly LiteFS startup to run database migrations using the app’s locally installed Prisma CLI (
/myapp/node_modules/.bin/prisma migrate deploy) instead ofbunx prisma@7, avoiding on-start dependency downloads and reducing boot time/health-check timeouts.Written by Cursor Bugbot for commit 651c9d8. This will update automatically on new commits. Configure here.