what stackpulse tracks
Better Auth releases from GitHub
StackPulse watches Better Auth release notes and keeps the original source link close to every summary.
The most comprehensive authentication framework for TypeScript StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Better Auth release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This release introduces new features like request context support in `verifyIdToken` and GDPR compliance enhancements. It also includes numerous bug fixes across various packages, improving reliability and security.
Developers using `verifyIdToken` or needing GDPR compliance for cookies are directly affected.
Update to v1.6.24 to benefit from new features and security fixes.
This release introduces significant breaking changes for CAPTCHA, MCP, OAuth provider, and two-factor authentication. Key updates include OIDC back-channel logout support, explicit modeling of protected resources, and PKCE enforcement.
All users of MCP, OAuth provider, two-factor auth, and Electron integration are affected by breaking changes.
Review breaking changes carefully and follow migration steps before upgrading.
This release focuses on bug fixes across multiple packages, including improvements to rate limits, session handling, OAuth validation, and security enhancements.
Users relying on OAuth, SSO, or IP resolution features may be affected by these fixes.
Update to v1.6.21 to benefit from the latest bug fixes and security improvements.
This beta release introduces new token refresh configuration options and improves security with SSRF protection and ID token nonce binding fixes.
Users implementing OAuth flows or token refresh functionality are affected by these changes.
Review the security fixes and consider implementing the new refreshTokenParams configuration if needed.