[GH-ISSUE #4757] v1.3.x maintaince plan #18682

New Issue

GiteaMirror · 2026-04-15T17:16:16-05:00

GiteaMirror commented

2026-04-15 17:16:16 -05:00

Originally created by @himself65 on GitHub (Sep 18, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/4757

We want to improve the stability of each major/minor version. So after talking about it, we are not adding more features after v1.3.12.

The only new feature between 1.3.10~1.3.11 is the database transaction. Database transaction enabled by default causes some database regression for users. Sorry for the inconvenience; we have fixed this in 1.3.12 by turning it off by default. Even though it helps a lot with error handling but we should use it in the next minor version 1.4

Now, we are only adding plugin fixes and non-breaking features. And we have set the branch to 1.3.x-latest as the target branch.

If you think any bug is urgent to fix, feel free to re-post here.

Covered issues

https://github.com/better-auth/better-auth/milestone/6

Previous Versions

Originally created by @himself65 on GitHub (Sep 18, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/4757 We want to improve the stability of each major/minor version. So after talking about it, we are not adding more features after v1.3.12. The only new feature between 1.3.10~1.3.11 is the [database transaction](https://github.com/better-auth/better-auth/commit/7efd139b). Database transaction enabled by default causes some database regression for users. Sorry for the inconvenience; we have fixed this in 1.3.12 by turning it off by default. Even though it helps a lot with error handling but we should use it in the next minor version 1.4 Now, we are only adding plugin fixes and non-breaking features. And we have set the branch to `1.3.x-latest` as the target branch. **If you think any bug is urgent to fix, feel free to re-post here.** ### Covered issues https://github.com/better-auth/better-auth/milestone/6 <details> <summary>Previous Versions</summary> #### 1.3.13 https://github.com/better-auth/better-auth/releases/tag/v1.3.13 #### 1.3.14 https://github.com/better-auth/better-auth/releases/tag/v1.3.14 #### 1.3.15 https://github.com/better-auth/better-auth/releases/tag/v1.3.15 </details> #### 1.3.24 https://github.com/better-auth/better-auth/releases/tag/v1.3.24

GiteaMirror added the locked label 2026-04-15 17:16:16 -05:00

GiteaMirror closed this issue

2026-04-15 17:16:17 -05:00

GiteaMirror commented

2026-04-15 17:16:18 -05:00

@linardsblk commented on GitHub (Sep 19, 2025):

Just updated from v1.3.7 to v1.3.12 in order to access the transactions feature but got blocked due incompatible node version (using v20.17). Usually these kind of breaking changes are reserved for major or at least minor version updates.

error @noble/hashes@2.0.0: The engine "node" is incompatible with this module. Expected version ">= 20.19.0". Got "20.17.0"

@linardsblk commented on GitHub (Sep 19, 2025): Just updated from v1.3.7 to v1.3.12 in order to access the transactions feature but got blocked due incompatible node version (using v20.17). Usually these kind of breaking changes are reserved for major or at least minor version updates. `error @noble/hashes@2.0.0: The engine "node" is incompatible with this module. Expected version ">= 20.19.0". Got "20.17.0"`

GiteaMirror commented

2026-04-15 17:16:18 -05:00

@himself65 commented on GitHub (Sep 19, 2025):

Just updated from v1.3.7 to v1.3.12 in order to access the transactions feature but got blocked due incompatible node version (using v20.17). Usually these kind of breaking changes are reserved for major or at least minor version updates.

error @noble/hashes@2.0.0: The engine "node" is incompatible with this module. Expected version ">= 20.19.0". Got "20.17.0"

We don't consider the non-LTS Node.js version support. Please bump the version

@himself65 commented on GitHub (Sep 19, 2025): > Just updated from v1.3.7 to v1.3.12 in order to access the transactions feature but got blocked due incompatible node version (using v20.17). Usually these kind of breaking changes are reserved for major or at least minor version updates. > > `error @noble/hashes@2.0.0: The engine "node" is incompatible with this module. Expected version ">= 20.19.0". Got "20.17.0"` We don't consider the non-LTS Node.js version support. Please bump the version

GiteaMirror commented

2026-04-15 17:16:19 -05:00

@coderrshyam commented on GitHub (Sep 20, 2025):

@himself65 The way versioning is being done feels a bit unprofessional.

Instead of creating many sub-versions under the same minor release, it’s better to release proper versions like 1.3, 1.4, and so on.

For urgent code changes like bug fixes, release a patch version.
For small new features, a minor version is sufficient.
For bigger features or any breaking changes, release a major version.

Also, for small patch updates, there’s no need to use Canary releases — you can keep it simple by following the Next.js release pattern.

@coderrshyam commented on GitHub (Sep 20, 2025): @himself65 The way versioning is being done feels a bit **unprofessional**. Instead of creating many sub-versions under the same minor release, it’s better to release proper versions like `1.3`, `1.4`, and so on. - For **urgent code changes** like bug fixes, release a **patch version**. - For **small new features**, a **minor version** is sufficient. - For **bigger features** or any **breaking changes**, release a **major version**. Also, for **small patch updates**, there’s no need to use **Canary releases** — you can keep it simple by following the **Next.js release pattern**.

GiteaMirror commented

2026-04-15 17:16:22 -05:00

@nadilas commented on GitHub (Sep 21, 2025):

@himself65 can we get c448ac0407 out fast?

containing https://github.com/better-auth/better-auth/pull/4765

@nadilas commented on GitHub (Sep 21, 2025): @himself65 can we get c448ac040706ec481055463d8f33edb8aef7f23d out fast? containing https://github.com/better-auth/better-auth/pull/4765

GiteaMirror commented

2026-04-15 17:16:25 -05:00

@himself65 commented on GitHub (Sep 22, 2025):

@himself65 The way versioning is being done feels a bit unprofessional.

Instead of creating many sub-versions under the same minor release, it’s better to release proper versions like 1.3, 1.4, and so on.

For urgent code changes like bug fixes, release a patch version.

For small new features, a minor version is sufficient.

For bigger features or any breaking changes, release a major version.

Also, for small patch updates, there’s no need to use Canary releases — you can keep it simple by following the Next.js release pattern.

Yeah, you are right. That's why we are trying to stabilize things in the coming version. We are concern and prioritize users' feedback and maintainability. We definitely will have clear versioning and a migration guide for coming new things coming

@himself65 commented on GitHub (Sep 22, 2025): > [@himself65](https://github.com/himself65) The way versioning is being done feels a bit **unprofessional**. > > Instead of creating many sub-versions under the same minor release, it’s better to release proper versions like `1.3`, `1.4`, and so on. > > * For **urgent code changes** like bug fixes, release a **patch version**. > * For **small new features**, a **minor version** is sufficient. > * For **bigger features** or any **breaking changes**, release a **major version**. > > Also, for **small patch updates**, there’s no need to use **Canary releases** — you can keep it simple by following the **Next.js release pattern**. Yeah, you are right. That's why we are trying to stabilize things in the coming version. We are concern and prioritize users' feedback and maintainability. We definitely will have clear versioning and a migration guide for coming new things coming

GiteaMirror commented

2026-04-15 17:16:26 -05:00

@himself65 commented on GitHub (Sep 22, 2025):

@himself65 can we get c448ac0 out fast?

containing #4765

Please check 1.3.14

@himself65 commented on GitHub (Sep 22, 2025): > [@himself65](https://github.com/himself65) can we get [c448ac0](https://github.com/better-auth/better-auth/commit/c448ac040706ec481055463d8f33edb8aef7f23d) out fast? > > containing [#4765](https://github.com/better-auth/better-auth/pull/4765) Please check 1.3.14

GiteaMirror commented

2026-04-15 17:16:27 -05:00

@nadilas commented on GitHub (Sep 23, 2025):

do you think it is related to the new patch that the schema generation doesn't run after upgrade?

2025-09-23T03:40:09.339Z ERROR [Better Auth]: [#better-auth]: Couldn't read your auth config. TypeError: z.coerce.boolean(...).meta is not a function
    at file:///Users/nadilas/workspace/.../node_modules/better-auth/dist/shared/better-auth.CBY7cUGy.mjs:61:44


const getSessionQuerySchema = z.optional(
  z.object({
    /**
     * If cookie cache is enabled, it will disable the cache
     * and fetch the session from the database
     */
>>>>    disableCookieCache: z.coerce.boolean().meta({
      description: "Disable cookie cache and fetch session from database"
    }).optional(),
    disableRefresh: z.coerce.boolean().meta({
      description: "Disable session refresh. Useful for checking session status, without updating the session"
    }).optional()
  })
);

@nadilas commented on GitHub (Sep 23, 2025): do you think it is related to the new patch that the schema generation doesn't run after upgrade? ``` 2025-09-23T03:40:09.339Z ERROR [Better Auth]: [#better-auth]: Couldn't read your auth config. TypeError: z.coerce.boolean(...).meta is not a function at file:///Users/nadilas/workspace/.../node_modules/better-auth/dist/shared/better-auth.CBY7cUGy.mjs:61:44 const getSessionQuerySchema = z.optional( z.object({ /** * If cookie cache is enabled, it will disable the cache * and fetch the session from the database */ >>>> disableCookieCache: z.coerce.boolean().meta({ description: "Disable cookie cache and fetch session from database" }).optional(), disableRefresh: z.coerce.boolean().meta({ description: "Disable session refresh. Useful for checking session status, without updating the session" }).optional() }) ); ```

GiteaMirror commented

2026-04-15 17:16:28 -05:00

@himself65 commented on GitHub (Sep 23, 2025):

do you think it is related to the new patch that the schema generation doesn't run after upgrade?

2025-09-23T03:40:09.339Z ERROR [Better Auth]: [#better-auth]: Couldn't read your auth config. TypeError: z.coerce.boolean(...).meta is not a function
    at file:///Users/nadilas/workspace/.../node_modules/better-auth/dist/shared/better-auth.CBY7cUGy.mjs:61:44


const getSessionQuerySchema = z.optional(
  z.object({
    /**
     * If cookie cache is enabled, it will disable the cache
     * and fetch the session from the database
     */
>>>>    disableCookieCache: z.coerce.boolean().meta({
      description: "Disable cookie cache and fetch session from database"
    }).optional(),
    disableRefresh: z.coerce.boolean().meta({
      description: "Disable session refresh. Useful for checking session status, without updating the session"
    }).optional()
  })
);

Please check Zod version, the function in v3 and v4 has a lot of change

@himself65 commented on GitHub (Sep 23, 2025): > do you think it is related to the new patch that the schema generation doesn't run after upgrade? > > ``` > 2025-09-23T03:40:09.339Z ERROR [Better Auth]: [#better-auth]: Couldn't read your auth config. TypeError: z.coerce.boolean(...).meta is not a function > at file:///Users/nadilas/workspace/.../node_modules/better-auth/dist/shared/better-auth.CBY7cUGy.mjs:61:44 > > > const getSessionQuerySchema = z.optional( > z.object({ > /** > * If cookie cache is enabled, it will disable the cache > * and fetch the session from the database > */ > >>>> disableCookieCache: z.coerce.boolean().meta({ > description: "Disable cookie cache and fetch session from database" > }).optional(), > disableRefresh: z.coerce.boolean().meta({ > description: "Disable session refresh. Useful for checking session status, without updating the session" > }).optional() > }) > ); > ``` Please check Zod version, the function in v3 and v4 has a lot of change

GiteaMirror commented

2026-04-15 17:16:29 -05:00

@nadilas commented on GitHub (Sep 23, 2025):

Yeah, exactly my thinking. I already upgraded from zod@v3 to zod@v4, same error though. 🤔

....except 1 package out of 11 packages. 😂 👍 resolved

@nadilas commented on GitHub (Sep 23, 2025): Yeah, exactly my thinking. I already upgraded from zod@v3 to zod@v4, same error though. 🤔 ....except 1 package out of 11 packages. 😂 👍 resolved

GiteaMirror commented

2026-04-15 17:16:30 -05:00

@jippi commented on GitHub (Sep 23, 2025):

I filed #4837 for the Zod 3 issue

@jippi commented on GitHub (Sep 23, 2025): I filed #4837 for the Zod 3 issue

GiteaMirror commented

2026-04-15 17:16:31 -05:00

@Ziothh commented on GitHub (Oct 7, 2025):

@himself65 Would it be possible to release the changes from #4919 in a v1.3.x version?
It solves #4453, which is also a blocking feature for my company to move from next-auth to better-auth.

I know it's in 1.4.0-beta.8, but it's a hard sell to use beta versions in production :)

@Ziothh commented on GitHub (Oct 7, 2025): @himself65 Would it be possible to release the changes from #4919 in a `v1.3.x` version? It solves #4453, which is also a blocking feature for my company to move from next-auth to better-auth. I know it's in [1.4.0-beta.8](https://www.npmjs.com/package/better-auth/v/1.4.0-beta.8), but it's a hard sell to use beta versions in production :)

GiteaMirror commented

2026-04-15 17:16:32 -05:00

@himself65 commented on GitHub (Oct 7, 2025):

@himself65 Would it be possible to release the changes from #4919 in a v1.3.x version? It solves #4453, which is also a blocking feature for my company to move from next-auth to better-auth.

I know it's in 1.4.0-beta.8, but it's a hard sell to use beta versions in production :)

I think we already have the commit in the 1.3 branch. No?

@himself65 commented on GitHub (Oct 7, 2025): > [@himself65](https://github.com/himself65) Would it be possible to release the changes from [#4919](https://github.com/better-auth/better-auth/pull/4919) in a `v1.3.x` version? It solves [#4453](https://github.com/better-auth/better-auth/issues/4453), which is also a blocking feature for my company to move from next-auth to better-auth. > > I know it's in [1.4.0-beta.8](https://www.npmjs.com/package/better-auth/v/1.4.0-beta.8), but it's a hard sell to use beta versions in production :) I think we already have the commit in the 1.3 branch. No?

GiteaMirror commented

2026-04-15 17:16:33 -05:00

@himself65 commented on GitHub (Nov 13, 2025):

We are release 1.4 soon

@himself65 commented on GitHub (Nov 13, 2025): We are release 1.4 soon

Sign in to join this conversation.

Branches Tags

feat/database-compound-indexes

changeset-release/next

main

feat/scim-demo-workflow

fix/oauth-provider-session-deletion

feat/scim-active-user-link

feat/sso-provider-user-resolution

feat/identity-provider-accounts

feat/issuer-scoped-account-identity

feat/oauth-provider-remove-silence-warnings

dependabot/npm_and_yarn/undici-7.28.0

dependabot/npm_and_yarn/vite-7.3.5

dependabot/github_actions/github-actions-62954de4be

dependabot/npm_and_yarn/demo/electron/demo-minor-patch-4169bf3d8e

changeset-release/release/vercel-announcement

release/vercel-announcement

2026-06-29/docs/optimize-og-images

feat/yandex-social-provider

feat/ssrf-fetch-boundary

codex/issue-8116-siwe-analysis

codex/pr-10225-next-comments

fix/phone-number-disable-input

perf/router-build-once

fix/oauth-user-provisioning-fields

codex/ignore-compose-override-spellcheck

2026-06-19/fix/stripe-org-reference-scope

feat/webhooks

feat/baseurl-canonical-serving-split

feat/magic-link-expires-in

fix/esbuild-security-bump

chore/sync-main-to-next-20260615

chore/revert-10053

codex/fix-expo-sdk56-dynamic-import

refactor/oauth-provider-client-authentication-module

fix/oauth-no-store-headers

claude/slack-update-stripe-docs-consistency-8Sc0w

local/fix-invite-accept-idempotency

docs/beta-mdx-component-fallback

fix/dependabot-hono-shell-quote

codex/stateless-account-cookie-resolution

fix/admin-create-user-role-escalation

feat/oauth-provider-oidc-acr

refactor/sign-in-challenges

refactor/optional-kysely-dependency

2026-06-06/chore/kysely-changeset

copilot/fix-code-review-comment

starsling/prisma-migration-reset

2026-06-02/fix/next-cookies-defer-rsc

feat/oauth-contribution-protocol

ping-maxwell/c-ping-maxwell/fix-kysely-adapter-core-utils-string-resolution-68c5

temp/server-only-test

2026-05-31/refactor/kysely-joins-json-helpers

2026-04-29/feat/google-include-granted-scopes

2026-04-29/fix/oauth-account-scope-semantics

fix/oauth-callback-path-declarative

2026-05-31/fix/sqlite-dialect-affected-rows

fix/next-cookie-separator

2026-05-29/fix/last-login-method-cookie-prefix

feat/oauth-provider-custom-subject

ping-maxwell/c-ping-maxwell/fix-error-link-apostrophe-f89a

client-assertions-main

2026-05-15/ci/fix-sqlite-abi-mismatch

2026-05-15/fix/organization-team-add-cascade

2026-05-15/fix/parse-set-cookie-value-validation

2026-05-13/feat/captcha-wildcard-endpoints

fix/i18n-before-hook-translation

fix/disable-migration-generate

2026-05-10/fix/cookie-drain-order

2026-05-10/feat/hooks-finally

2026-05-09/fix/cookie-drain-order

2026-05-09/feat/hooks-finally

2026-05-08/feat/register-before-send

fix/stripe/subscription-data-merge

2026-05-01/chore/pnpm-v11-harden

chore/pnpm-v11

2026-04-27/fix/nextcookies-idempotent-writes

2026-04-26/fix/harden-proxy-host-validation

2026-04-26/refactor/stripe-callback-signature-cleanup

2026-04-26/fix/stripe-subscription-callback-timing

2026-04-11/fix/sveltekit-app-modules

feat/open-api-zod-contract

feat/oauth-idp-initiated-bounce

2026-04-21/fix/oauth-rfc-input-validation

fix/two-factor-identity-guard

fix/resource

feat/emailpassword-authorize

feat/oauth-provider-at-hash-v2

fix/release-grep-fallback

claude/address-review-comments-JhFLr

feat/async-auth

fix/two-factor-totp-verified-enrollment

feat/plugin-ui

codex/blog-1-6-release-post

2026-04-06/fix/type-any-guards

2026-04-05/chore/downgrade-better-call

2026-04-04/ci/skip-vercel-fork-prs

2026-03-28/ci/add-autofix-ci

chore/release-preview-script

himself65/2026/02/19/role

2026-03-20/docs/improve-website

2026-03-20/fix/anonymous-onlinkaccount-expo

2026-02-17/fix/anonymous-link-state

fix/8607-saml-inresponseto

fix/8549-scim-patch-noop

v1.4.x

refactor/migration-snapshot-tests

worktree-magic-link-additional-data

chore/migrate-build-to-rollup

worktree-fix-dynamic-baseurl-8447

2026-03-06/chore/public-api-check

fix/close-8156-regression-test

fix/secondary-storage-json-error-handling

himself65/verification-namespace

cursor/issue-8307-validation-79a3

himself65/2026/01/30/error-mdx

v1.4.x-staging

fix/email-otp-user

fix/restrict-full-organization-access-roles

himself65/2026/02/12/count

himself65/2026/02/04/define-plugin

2026-02-04/feat/add-pluralize

cursor/better-auth-js-integration-ec21

cursor/expo-state-mismatch-394c

2026-02-01/fix/org-update-role-sync-members

cursor/issue-7607-investigation-e146

cursor/email-generation-helper-0ff6

himself65/2026/01/21/avoid-spread-operator

himself65/2026/01/14/cli

claude/slack-add-docs-pr-NMvgO

claude/slack-add-advanced-useplural-WHKYL

feat/hooks-pos

feat/2fa-phone

feat/2fa

fix/rotation

fix/username-check

v1.3.x

refactor/organization

feat/multiple-client-ids-social-providers

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/better-auth#18682