Packages

@better-auth/cimd

1.7.12 · 20 Oct 2026MIT385.2k / weekRepositoryHomepagenpmAtom feed

13 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.

  1. 1.7.12

    20 Oct 2026
    • Fixed the JWT plugin to verify JWTs and session cookie-cache JWTs with the stored key's algorithm instead of the token header's, and to warn when signing or verifying a JWT without an issuer or audience

    • Fixed OAuth callbacks completed through the OAuth proxy to run the same checks as the standard OAuth callback, including issuer and ID token nonce validation

    • Fixed auth.api.getSession() to keep the original database error as error.cause when the session lookup fails

  2. 1.7.11

    19 Oct 2026
    • Fixed repeated PostgreSQL migration diffs for int8 columns.

    • Fixed database-backed rate limiting returning an excessively large X-Retry-After value.

    • Fixed plugin init returns with options: undefined failing type checks under exactOptionalPropertyTypes.

  3. 1.7.10

    15 Oct 2026
    • Fixed Captcha and OpenAPI plugin subpath imports and type resolution for better-auth/plugins/multi-session and better-auth/test.

    • Fixed Google One Tap sign-ins not recording google as the last login method.

    • Fixed imports from better-auth/plugins/one-tap failing with a not-exported error.

  4. 1.7.9

    15 Oct 2026
    • Fixed onAPIError.onError handlers to finish before responses are sent and log failures without interrupting requests

    • Added isContinuation to postLogin.shouldRedirect so users can complete authorization after selecting an organization

    • Fixed DPoP validation for token and UserInfo requests behind proxies that rewrite request URLs

  5. 1.7.8

    14 Oct 2026
    • Added support for host-bearing custom-scheme redirect URIs for native OAuth clients

  6. 1.7.7

    30 Sep 2026
    • security

      Fixed a critical Magic Link account-takeover vulnerability.

    • Fixed ID-token sign-in ignoring the social provider’s disableSignUp setting.

    • Fixed OAuth Proxy accepting sign-in state as a provider profile.
      Upgrade all OAuth Proxy participants together; see the OAuth Proxy upgrade guidance.

  7. 1.7.6

    24 Sep 2026
    • Added support for a bannedUserMessage function that receives the banned user, allowing sign-in errors to include details such as the ban reason.

    • Added Vercel BotID as a captcha provider for protected authentication routes.

    • Passwords over maxPasswordLength are now rejected with PASSWORD_TOO_LONG before hashing or verification.

  8. 1.7.5

    14 Sep 2026
    • Fixed unnecessary pacing of consecutive CIMD OAuth requests when metadata cannot be cached.

  9. 1.7.4

    10 Sep 2026
    • Added experimental.instrumentation.enabled to disable OpenTelemetry span creation per auth instance.

    • Added support for additional session fields in testUtils auth helpers.

    • Added Vitest 5 support to the testing utilities.

  10. 1.7.3

    6 Sep 2026
    • Fixed CIMD client metadata discovery failures with ERR_INVALID_IP_ADDRESS on supported Node.js versions.

  11. 1.7.2

    26 Aug 2026
    • Fixed permanent user bans to clear expiration dates from previous temporary bans.

    • Fixed client types with more plugins being assignable to types declaring fewer plugins.

    • Added warnings for invalid signed session data in the cookie cache.

  12. 1.7.1

    18 Aug 2026
    • Fixed Client ID Metadata Document caching to follow shared-cache freshness rules: the plugin now prefers s-maxage over max-age and Expires, honors s-maxage=0, conditionally revalidates with ETag or Last-Modified, and treats invalid or duplicate freshness directives as immediately stale. Concurrent refreshes now converge on a single client-resource link instead of failing on a unique constraint.

  13. 1.7.0

    18 Aug 2026
    • breaking

      Aligned OAuth client registration and metadata with MCP authorization 2026-07-28

      Migration: Add applicationType and nullable clientDiscoveryId columns, deduplicate existing (clientId, resourceId) links before the new compound unique index, then drop the legacy type and public columns. Client ID Metadata Documents preserve an omitted application_type as null and cannot assign clientCredentialsScopes. Compose mcp() with cimd() for metadata-document clients.

    • Added the @better-auth/cimd Client ID Metadata Document plugin

    • Client ID Metadata Documents now follow shared-cache freshness rules and fail closed when freshness is ambiguous. The plugin prefers s-maxage over max-age and Expires, honors s-maxage=0, revalidates conditionally with ETag or Last-Modified, and treats invalid or duplicate freshness directives as immediately stale. Concurrent refreshes converge on one client-resource link instead of failing on its unique constraint.