github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 23:52:05 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #5669] [MERGED] docs: update migration guide from Supabase Auth #23050

New Issue
Closed
opened 2026-04-15 21:26:58 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 21:26:58 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/5669
Author: @bytaesu
Created: 10/30/2025
Status: ✅ Merged
Merged: 10/30/2025
Merged by: @Bekacru

Base: canary ← Head: 2025-10-30/docs/supabase-guide

📝 Commits (4)

📊 Changes

1 file changed (+801 additions, -136 deletions)

View changed files

📝 docs/content/docs/guides/supabase-migration-guide.mdx (+801 -136)

📄 Description

This PR updates the content for migrating from Supabase Auth to Better Auth.

Summary by cubic

Updated the Supabase Auth → Better Auth migration guide with clearer setup requirements and a robust, resumable migration script to reduce data loss and handle large datasets safely.

  • New Features
    • Made email/password required and added guidance to include admin, anonymous, and phoneNumber plugins.
    • Added required user.additionalFields (userMetadata, appMetadata, invitedAt, lastSignInAt).
    • Clarified social provider setup: include all providers used in Supabase to avoid missing accounts.
    • Introduced a new migration script with batching, cursor resume (resumeFromId), progress/ETA, transactions, and temp emails for phone-only users.
    • Added environment variables (FROM_DATABASE_URL, TO_DATABASE_URL) and noted tables are created in the public schema via the CLI migrate command.

Written for commit 68cb3fb. Summary will update automatically on new commits.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/5669 **Author:** [@bytaesu](https://github.com/bytaesu) **Created:** 10/30/2025 **Status:** ✅ Merged **Merged:** 10/30/2025 **Merged by:** [@Bekacru](https://github.com/Bekacru) **Base:** `canary` ← **Head:** `2025-10-30/docs/supabase-guide` --- ### 📝 Commits (4) - [`d3aa995`](https://github.com/better-auth/better-auth/commit/d3aa995670df76807a359bfbd06169937094dcca) docs: update migration guide from Supabase Auth - [`b254c76`](https://github.com/better-auth/better-auth/commit/b254c76643abb4d34a9b071d6551d488959bbceb) docs: adjust content - [`2a15755`](https://github.com/better-auth/better-auth/commit/2a15755f08bfeddabef0e53b11c6a62efc01808c) fix: code indentation - [`68cb3fb`](https://github.com/better-auth/better-auth/commit/68cb3fbc603f67a736233e9502a06f5de5c65317) fix: imports ### 📊 Changes **1 file changed** (+801 additions, -136 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/guides/supabase-migration-guide.mdx` (+801 -136) </details> ### 📄 Description This PR updates the content for migrating from Supabase Auth to Better Auth. <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Updated the Supabase Auth → Better Auth migration guide with clearer setup requirements and a robust, resumable migration script to reduce data loss and handle large datasets safely. - **New Features** - Made email/password required and added guidance to include admin, anonymous, and phoneNumber plugins. - Added required user.additionalFields (userMetadata, appMetadata, invitedAt, lastSignInAt). - Clarified social provider setup: include all providers used in Supabase to avoid missing accounts. - Introduced a new migration script with batching, cursor resume (resumeFromId), progress/ETA, transactions, and temp emails for phone-only users. - Added environment variables (FROM_DATABASE_URL, TO_DATABASE_URL) and noted tables are created in the public schema via the CLI migrate command. <sup>Written for commit 68cb3fb. Summary will update automatically on new commits.</sup> <!-- End of auto-generated description by cubic. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-15 21:26:58 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#23050
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?