Repository navigation
v2.5.3
🔒 A security update: Better Auth 1.7.18, Next.js 16.4.5, and five fixes in how the kit enforces its own rules. Several rules lived only in the server actions behind the kit's forms, so a request sent to the auth API directly did not meet them; they are now enforced where every request goes through. If you run the kit with email configured and two-factor authentication, with a public demo, or with one-time payments, update. A PATCH: git pull, npm install. Nothing to migrate. If you enable a delayed payment method in Stripe (SEPA, ACH, Bacs and the like), add the two events listed under Billing to your webhook endpoint.
Security
- Better Auth 1.7.18, with the fixes the project published on November 3 (see its security advisories). Among them, for features the kit uses: an OAuth email the provider did not verify, email change links, and revoked sessions with the cookie cache
- Next.js 16.4.5, with the fixes published on November 3 (see its security advisories)
- Two-factor accounts can no longer sign in with a magic link or with the automatic sign-in after verifying an email, whichever way the request arrives. The magic link endpoint also keeps the per-address limit when it is called directly
- On a public demo (
DEMO_MODE), what the demo's actions refuse is refused over the auth API too: listing or ending sessions, two-factor setup, deleting the account, changing its email or password, signing up and resetting a password. The Active sessions card is unchanged - Names are escaped in every email (welcome, subscription, purchase, cancellation), as the contact and invitation emails already were. A display name is capped at 100 characters wherever it is set, and may not contain a web address, which mail clients would turn into a link: the forms say so, and a name sent to the auth API directly is replaced
- A one-time purchase is granted once it is paid. With a delayed payment method the checkout completes before the money arrives; the purchase now waits for
checkout.session.async_payment_succeeded, andcheckout.session.async_payment_failedgrants nothing. Card payments behave as before - The newsletter export writes cells that start with
=,+,-or@as text, and the signup'ssourcekeeps only the labels the kit's forms send; anything else falls back to the default and the address is still recorded