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

[PR #3179] [CLOSED] Fix/3138 stripe updatedAt #21593

New Issue
Closed
opened 2026-04-15 20:28:35 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 20:28:35 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/3179
Author: @tinkerer-shubh
Created: 6/26/2025
Status: ❌ Closed

Base: main ← Head: fix/3138-stripe-updatedAt

📝 Commits (2)

  • 419427e feat(stripe): add createdAt and updatedAt fields to subscription schema and types
  • 2a57171 fix(stripe): ensure updatedAt timestamp is refreshed on every subscription/user update

📊 Changes

3 files changed (+22 additions, -0 deletions)

View changed files

📝 packages/stripe/src/index.ts (+4 -0)
📝 packages/stripe/src/schema.ts (+10 -0)
📝 packages/stripe/src/types.ts (+8 -0)

📄 Description

Purpose:
This PR fixes missing timestamp columns that caused updatedAt write errors in the Stripe plugin and ensures the updatedAt field is kept in sync on every mutation.

Summary of Changes:

  1. schema.ts

    • Added createdAt and updatedAt fields to the subscription model.
    • Both fields now have a default value of new Date(), ensuring new subscriptions always get timestamped.

  2. types.ts

    • The Subscription interface now includes optional createdAt and updatedAt properties.
    • This allows for type-safe use of these fields throughout the codebase.

  3. index.ts (Stripe plugin logic)

    • Updated several code paths using adapter.update to explicitly set updatedAt: new Date():
      • Customer creation
      • Cancel-at-period-end
      • Manual cancel fallback
      • Restore operation
    • This ensures the updatedAt field is always updated properly on relevant mutations.

closes: https://github.com/better-auth/better-auth/issues/3138

🔄 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/3179 **Author:** [@tinkerer-shubh](https://github.com/tinkerer-shubh) **Created:** 6/26/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/3138-stripe-updatedAt` --- ### 📝 Commits (2) - [`419427e`](https://github.com/better-auth/better-auth/commit/419427e60c30b793ec0f12449483bcc03483bfb2) feat(stripe): add createdAt and updatedAt fields to subscription schema and types - [`2a57171`](https://github.com/better-auth/better-auth/commit/2a57171b3f01f3c5262adf9aebd5055ae377b8f5) fix(stripe): ensure updatedAt timestamp is refreshed on every subscription/user update ### 📊 Changes **3 files changed** (+22 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `packages/stripe/src/index.ts` (+4 -0) 📝 `packages/stripe/src/schema.ts` (+10 -0) 📝 `packages/stripe/src/types.ts` (+8 -0) </details> ### 📄 Description **Purpose:** This PR fixes missing timestamp columns that caused `updatedAt` write errors in the Stripe plugin and ensures the `updatedAt` field is kept in sync on every mutation. **Summary of Changes:** 1. **schema.ts** - Added `createdAt` and `updatedAt` fields to the `subscription` model. - Both fields now have a default value of `new Date()`, ensuring new subscriptions always get timestamped. 2. **types.ts** - The `Subscription` interface now includes optional `createdAt` and `updatedAt` properties. - This allows for type-safe use of these fields throughout the codebase. 3. **index.ts** (Stripe plugin logic) - Updated several code paths using `adapter.update` to explicitly set `updatedAt: new Date()`: - Customer creation - Cancel-at-period-end - Manual cancel fallback - Restore operation - This ensures the `updatedAt` field is always updated properly on relevant mutations. closes: https://github.com/better-auth/better-auth/issues/3138 --- <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 20:28:35 -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#21593
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?