fix(better-auth): model migration ordering explicitly - #1379
Open
focux wants to merge 1 commit into
Open
Conversation
sam-goodwin
reviewed
Aug 27, 2026
Contributor
There was a problem hiding this comment.
if you change plan, you gotta add corresponding plan.test.ts cases to document and enforce this
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.
Better Auth placed its migration Action output in the host env only to establish ordering. Because Action outputs remain unresolved during planning, every later plan kept the host Worker dirty.
Track ordering-only outputs separately from provider props and use that dependency channel for migrations. This preserves migration → host ordering without deploying a runtime env value.
Tests:
Closes #1378