feat: support Better Auth 1.7 with atomic storage - #64
Open
zpg6 wants to merge 1 commit into
Open
Conversation
commit: |
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.
Follow-up to #62.
Better Auth 1.7 requires atomic
incrementandgetAndDelete, which KV cannot provide. This adds an optional Durable Object adapter without silently moving existing KV users onto a paid backend.The Hono example uses Durable Objects for secondary storage. OpenNext keeps KV for session caching, stores verification data in D1, and uses a Durable Object only for rate limiting. That split is intentional: each atomic operation routed through a Durable Object adds a request.
This also tightens the upgrade path. The CLI creates a fresh lockfile with the selected package manager, remote migrations require a separate reviewed command, and CI regenerates the Drizzle SQL, snapshot, and journal instead of trusting hand-edited migration files.
One sharp edge remains upstream: the generated 1.7 migration adds
accounts.issuerasNOT NULL. Anyone upgrading a populated 1.6 database still needs to back it up and rehearse that migration first.