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

[PR #67] [MERGED] feat: add new core table verification #28682

New Issue
Closed
opened 2026-04-17 20:09:42 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-17 20:09:42 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/67
Author: @Bekacru
Created: 10/2/2024
Status: ✅ Merged
Merged: 10/2/2024
Merged by: @Bekacru

Base: main ← Head: core-tables

📝 Commits (8)

📊 Changes

1 file changed (+9 additions, -25 deletions)

View changed files

📝 packages/better-auth/src/db/internal-adapter.ts (+9 -25)

📄 Description

It's better that we have a common generic table to store verification related data. This adds a verification table that consists fields

  • value
  • identifier
  • expiresAt

🔄 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/67 **Author:** [@Bekacru](https://github.com/Bekacru) **Created:** 10/2/2024 **Status:** ✅ Merged **Merged:** 10/2/2024 **Merged by:** [@Bekacru](https://github.com/Bekacru) **Base:** `main` ← **Head:** `core-tables` --- ### 📝 Commits (8) - [`e98cdeb`](https://github.com/better-auth/better-auth/commit/e98cdeb2605d8dceae222afeeb614479d7e42b41) wip - [`064ca66`](https://github.com/better-auth/better-auth/commit/064ca668fe39f12037b3cead68f4dc40b7d9cb96) feat: verification table - [`b205398`](https://github.com/better-auth/better-auth/commit/b205398c892a511264049ab2894d5bc77d94c200) hooks - [`787aceb`](https://github.com/better-auth/better-auth/commit/787aceb5a79643455f9fc3b317f1f779c66e62c8) docs: more doc - [`f9d83e5`](https://github.com/better-auth/better-auth/commit/f9d83e5a269f961a06ec217994588e702c41f0ee) Merge branch 'main' into core-tables - [`0ac6060`](https://github.com/better-auth/better-auth/commit/0ac60607463752a8980cc8faa0ee479b85639f5e) chore: remove unccessary test - [`8caf3e6`](https://github.com/better-auth/better-auth/commit/8caf3e6bd0ef404331a7c628987f8656908d4ea2) chore: release v0.2.8-beta.2 - [`31e96e6`](https://github.com/better-auth/better-auth/commit/31e96e6d0ebeb2f8d74ceb6f0b46ecfb46823923) Merge branch 'main' into core-tables ### 📊 Changes **1 file changed** (+9 additions, -25 deletions) <details> <summary>View changed files</summary> 📝 `packages/better-auth/src/db/internal-adapter.ts` (+9 -25) </details> ### 📄 Description It's better that we have a common generic table to store verification related data. This adds a verification table that consists fields - value - identifier - expiresAt --- <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 20:09:42 -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#28682
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?