[PR #6444] [MERGED] fix(docs): correct banExpires field and time unit in Clerk migration guide #23570

Closed
opened 2026-04-15 21:50:03 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/6444
Author: @GautamBytes
Created: 12/1/2025
Status: Merged
Merged: 12/1/2025
Merged by: @himself65

Base: canaryHead: docs/fix-clerk-migration-script


📝 Commits (1)

  • 6d99bb4 fix(docs): update Clerk migration script to use correct admin banExpires field

📊 Changes

1 file changed (+3 additions, -1 deletions)

View changed files

📝 docs/content/docs/guides/clerk-migration-guide.mdx (+3 -1)

📄 Description

Description

Fixes #6442

Updates the Clerk migration guide script to correctly map user ban data to the Admin plugin schema.

Changes

  • Renamed banExpiresAt to banExpires to match the correct Admin plugin schema.
  • Added logic to convert Clerk's lockout_expires_in_seconds (which is a duration in seconds) into a JavaScript Date object (timestamp), as the database adapter expects a Date.

Checklist

  • Documentation updated

Summary by cubic

Corrected the Clerk migration guide to use banExpires (not banExpiresAt) and to convert Clerk’s lockout_expires_in_seconds into a Date timestamp. Prevents incorrect admin ban data when migrating from Clerk.

Written for commit 6d99bb4a13. 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/6444 **Author:** [@GautamBytes](https://github.com/GautamBytes) **Created:** 12/1/2025 **Status:** ✅ Merged **Merged:** 12/1/2025 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `docs/fix-clerk-migration-script` --- ### 📝 Commits (1) - [`6d99bb4`](https://github.com/better-auth/better-auth/commit/6d99bb4a138dd7a07ad396689615d68c152fca06) fix(docs): update Clerk migration script to use correct admin banExpires field ### 📊 Changes **1 file changed** (+3 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/guides/clerk-migration-guide.mdx` (+3 -1) </details> ### 📄 Description ## Description Fixes #6442 Updates the Clerk migration guide script to correctly map user ban data to the Admin plugin schema. ## Changes - Renamed `banExpiresAt` to `banExpires` to match the correct Admin plugin schema. - Added logic to convert Clerk's `lockout_expires_in_seconds` (which is a duration in seconds) into a JavaScript `Date` object (timestamp), as the database adapter expects a Date. ## Checklist - [x] Documentation updated <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Corrected the Clerk migration guide to use banExpires (not banExpiresAt) and to convert Clerk’s lockout_expires_in_seconds into a Date timestamp. Prevents incorrect admin ban data when migrating from Clerk. <sup>Written for commit 6d99bb4a138dd7a07ad396689615d68c152fca06. 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:50:03 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#23570