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

[PR #5710] Update next-auth-migration-guide.mdx #31771

New Issue
Open
opened 2026-04-17 22:39:15 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-17 22:39:15 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/5710
Author: @kristianka
Created: 11/1/2025
Status: 🔄 Open

Base: main ← Head: patch-2

📝 Commits (4)

  • 765a28f Update next-auth-migration-guide.mdx
  • c658f81 Update docs/content/docs/guides/next-auth-migration-guide.mdx
  • 30e0197 Update next-auth-migration-guide.mdx
  • 178e630 Update next-auth-migration-guide.mdx

📊 Changes

1 file changed (+6 additions, -0 deletions)

View changed files

📝 docs/content/docs/guides/next-auth-migration-guide.mdx (+6 -0)

📄 Description

The migration docs from Next-auth / Auth.js is missing a step: renaming a table. Without this, the following error shows in the console:

2025-11-01T01:41:38.007Z ERROR [Better Auth]: Model verification does not exist in the database. If you haven't generated the Prisma client, you need to run 'npx prisma generate'
# SERVER_ERROR:  [Error [BetterAuthError]: Model verification does not exist in the database. If you haven't generated the Prisma client, you need to run 'npx prisma generate'] {
  cause: undefined
}

Summary by cubic

Added the missing migration step to rename the verification table from VerificationToken to Verification so Better Auth recognizes the model and avoids the “Model verification does not exist” error.

  • Migration
    • Rename the verification schema/table from VerificationToken to Verification and match ORM casing (verification or Verification).

Written for commit 178e630bc0. 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/5710 **Author:** [@kristianka](https://github.com/kristianka) **Created:** 11/1/2025 **Status:** 🔄 Open **Base:** `main` ← **Head:** `patch-2` --- ### 📝 Commits (4) - [`765a28f`](https://github.com/better-auth/better-auth/commit/765a28f7128e5949c2621a4fbd9cc1c8db03494a) Update next-auth-migration-guide.mdx - [`c658f81`](https://github.com/better-auth/better-auth/commit/c658f81e947ba948f11a065299d91f4accac8a69) Update docs/content/docs/guides/next-auth-migration-guide.mdx - [`30e0197`](https://github.com/better-auth/better-auth/commit/30e0197347e091680dcbd284edc78596b62c0a95) Update next-auth-migration-guide.mdx - [`178e630`](https://github.com/better-auth/better-auth/commit/178e630bc04442eb8050487d9c4e7714f65e7cf8) Update next-auth-migration-guide.mdx ### 📊 Changes **1 file changed** (+6 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/guides/next-auth-migration-guide.mdx` (+6 -0) </details> ### 📄 Description The migration docs from Next-auth / Auth.js is missing a step: renaming a table. Without this, the following error shows in the console: ```bash 2025-11-01T01:41:38.007Z ERROR [Better Auth]: Model verification does not exist in the database. If you haven't generated the Prisma client, you need to run 'npx prisma generate' # SERVER_ERROR: [Error [BetterAuthError]: Model verification does not exist in the database. If you haven't generated the Prisma client, you need to run 'npx prisma generate'] { cause: undefined } ``` <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Added the missing migration step to rename the verification table from VerificationToken to Verification so Better Auth recognizes the model and avoids the “Model verification does not exist” error. - **Migration** - Rename the verification schema/table from VerificationToken to Verification and match ORM casing (verification or Verification). <sup>Written for commit 178e630bc04442eb8050487d9c4e7714f65e7cf8. 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-17 22:39:15 -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#31771
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?