docs: clarify D1 migrations not run during build#734
Merged
atinux merged 1 commit intonuxt-hub:mainfrom Dec 19, 2025
Merged
Conversation
|
@onmax is attempting to deploy a commit to the NuxtLabs Team on Vercel. A member of the Team first needs to authorize it. |
commit: |
Contributor
|
Same as #732, are you happy to move your changes to the new structure? 🙏 |
onmax
force-pushed
the
docs/d1-migrations-warning
branch
from
5667aac to
c0c6ddf
Compare
atinux
approved these changes
Dec 19, 2025
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
2 participants
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.
Docs said migrations run during build, but D1 forces
applyMigrationsDuringBuild: falsesince there's no DB connection in CI.Added warning callout to clarify users must run
npx nuxt db migratemanually for D1.