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

[PR #3635] [MERGED] fix(stripe): update customer id should also trigger secondary storage update #30526

New Issue
Closed
opened 2026-04-17 21:35:13 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-17 21:35:13 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/3635
Author: @Bekacru
Created: 7/26/2025
Status: ✅ Merged
Merged: 7/26/2025
Merged by: @Bekacru

Base: main ← Head: fix/stripe-customer

📝 Commits (2)

  • f75c095 fix: update customer id should also update secondary storage
  • 4aacc47 chore: add changeset

📊 Changes

4 files changed (+11 additions, -29 deletions)

View changed files

➕ .changeset/huge-needles-smell.md (+5 -0)
📝 docs/content/docs/concepts/users-accounts.mdx (+1 -2)
📝 packages/stripe/src/index.ts (+5 -17)
📝 packages/stripe/src/types.ts (+0 -10)

📄 Description

Summary by cubic

Updating a user's Stripe customer ID now also updates the secondary storage to keep user data in sync.

  • Refactors
    • Removed the old Customer type and related code.
    • Switched to using internalAdapter.updateUser for updating the Stripe customer ID.

🔄 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/3635 **Author:** [@Bekacru](https://github.com/Bekacru) **Created:** 7/26/2025 **Status:** ✅ Merged **Merged:** 7/26/2025 **Merged by:** [@Bekacru](https://github.com/Bekacru) **Base:** `main` ← **Head:** `fix/stripe-customer` --- ### 📝 Commits (2) - [`f75c095`](https://github.com/better-auth/better-auth/commit/f75c0959f432f50a1562cf0b01d9ddf0f8a1c6a4) fix: update customer id should also update secondary storage - [`4aacc47`](https://github.com/better-auth/better-auth/commit/4aacc47b8d4bd6cee2d6a92eda332de72a928be0) chore: add changeset ### 📊 Changes **4 files changed** (+11 additions, -29 deletions) <details> <summary>View changed files</summary> ➕ `.changeset/huge-needles-smell.md` (+5 -0) 📝 `docs/content/docs/concepts/users-accounts.mdx` (+1 -2) 📝 `packages/stripe/src/index.ts` (+5 -17) 📝 `packages/stripe/src/types.ts` (+0 -10) </details> ### 📄 Description <!-- This is an auto-generated description by cubic. --> ## Summary by cubic Updating a user's Stripe customer ID now also updates the secondary storage to keep user data in sync. - **Refactors** - Removed the old Customer type and related code. - Switched to using internalAdapter.updateUser for updating the Stripe customer ID. <!-- 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 21:35:13 -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#30526
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?