[GH-ISSUE #4187] $onUpdate is not set for updatedAt field in psql schema #9855

New Issue

GiteaMirror · 2026-04-13T05:37:39-05:00

GiteaMirror commented

2026-04-13 05:37:39 -05:00

Originally created by @yvbbrjdr on GitHub (Aug 24, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/4187

Is this suited for github?

Yes, this is suited for github

To Reproduce

Setup better-auth with drizzle (provider=pg).
Run npx @better-auth/cli generate.

Current vs. Expected behavior

Currently, it outputs a schema which looks like

// ...

export const user = pgTable("user", {
  id: text("id").primaryKey(),
  name: text("name").notNull(),
  email: text("email").notNull().unique(),
  emailVerified: boolean("email_verified")
    .$defaultFn(() => false)
    .notNull(),
  image: text("image"),
  createdAt: timestamp("created_at")
    .$defaultFn(() => /* @__PURE__ */ new Date())
    .notNull(),
  updatedAt: timestamp("updated_at")
    .$defaultFn(() => /* @__PURE__ */ new Date())
    .notNull(),
});

// ...

For the updatedAt field, it's missing

    .$onUpdate(() => /* @__PURE__ */ new Date())

What version of Better Auth are you using?

1.3.7

System info

System:
    OS: macOS 26.0
    CPU: (8) arm64 Apple M1 Pro
    Memory: 101.58 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh

Which area(s) are affected? (Select all that apply)

Backend

Auth config (if applicable)

import { betterAuth } from "better-auth"
export const auth = betterAuth({
  emailAndPassword: {  
    enabled: true
  },
  database: drizzleAdapter(db, {
    provider: "pg",
  }),
});

Additional context

No response

Originally created by @yvbbrjdr on GitHub (Aug 24, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/4187 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce 1. Setup better-auth with drizzle (provider=pg). 2. Run `npx @better-auth/cli generate`. ### Current vs. Expected behavior Currently, it outputs a schema which looks like ```typescript // ... export const user = pgTable("user", { id: text("id").primaryKey(), name: text("name").notNull(), email: text("email").notNull().unique(), emailVerified: boolean("email_verified") .$defaultFn(() => false) .notNull(), image: text("image"), createdAt: timestamp("created_at") .$defaultFn(() => /* @__PURE__ */ new Date()) .notNull(), updatedAt: timestamp("updated_at") .$defaultFn(() => /* @__PURE__ */ new Date()) .notNull(), }); // ... ``` For the `updatedAt` field, it's missing ```typescript .$onUpdate(() => /* @__PURE__ */ new Date()) ``` ### What version of Better Auth are you using? 1.3.7 ### System info ```bash System: OS: macOS 26.0 CPU: (8) arm64 Apple M1 Pro Memory: 101.58 MB / 16.00 GB Shell: 5.9 - /bin/zsh ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" export const auth = betterAuth({ emailAndPassword: { enabled: true }, database: drizzleAdapter(db, { provider: "pg", }), }); ``` ### Additional context _No response_

GiteaMirror added the locked bug labels 2026-04-13 05:37:39 -05:00

GiteaMirror closed this issue

2026-04-13 05:37:40 -05:00

GiteaMirror commented

2026-04-13 05:37:42 -05:00

@dosubot[bot] commented on GitHub (Aug 24, 2025):

Hi @yvbbrjdr! I'm Dosu and I’m helping the better-auth team.

The omission of .$onUpdate(() => new Date()) for the updatedAt field in the generated Drizzle schema is not intentional or documented—it's likely an oversight in the schema template logic. Without .$onUpdate, the updatedAt field won't automatically update when records are modified, which is the expected behavior for most user/auth tables in Drizzle ORM.

To fix this, manually add .$onUpdate(() => new Date()) to the updatedAt field in your generated schema. This will ensure the timestamp updates correctly on record changes. There are no tickets or docs explaining this omission, and recent code and test snapshots confirm it's still missing in the latest release (source). If you want official support for this, you could suggest it for a future release.

Let me know if you need help with the implementation or have other questions!

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Aug 24, 2025):  Hi @yvbbrjdr! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the better-auth team.  The omission of `.$onUpdate(() => new Date())` for the `updatedAt` field in the generated Drizzle schema is not intentional or documented—it's likely an oversight in the schema template logic. Without `.$onUpdate`, the `updatedAt` field won't automatically update when records are modified, which is the expected behavior for most user/auth tables in Drizzle ORM. To fix this, manually add `.$onUpdate(() => new Date())` to the `updatedAt` field in your generated schema. This will ensure the timestamp updates correctly on record changes. There are no tickets or docs explaining this omission, and recent code and test snapshots confirm it's still missing in the latest release ([source](https://github.com/better-auth/better-auth/pull/4132)). If you want official support for this, you could suggest it for a future release. Let me know if you need help with the implementation or have other questions!  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/a681c16d-ffb9-499a-a106-f488e880b5c6?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/a681c16d-ffb9-499a-a106-f488e880b5c6?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/a681c16d-ffb9-499a-a106-f488e880b5c6?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/a681c16d-ffb9-499a-a106-f488e880b5c6?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a681c16d-ffb9-499a-a106-f488e880b5c6?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/a681c16d-ffb9-499a-a106-f488e880b5c6?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a681c16d-ffb9-499a-a106-f488e880b5c6?feedback_type=other)</sup>  [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/4187)

GiteaMirror commented

2026-04-13 05:37:43 -05:00

@yvbbrjdr commented on GitHub (Aug 24, 2025):

@dosu

expected behavior for most user/auth tables in Drizzle ORM

Why?

@yvbbrjdr commented on GitHub (Aug 24, 2025): @dosu > expected behavior for most user/auth tables in Drizzle ORM Why?

GiteaMirror commented

2026-04-13 05:37:43 -05:00

@dosubot[bot] commented on GitHub (Aug 24, 2025):

It's considered best practice in most ORMs and relational databases to auto-update the updatedAt field whenever a record changes, especially for user/auth tables. This helps with auditability, debugging, and compliance—knowing when data was last modified is crucial for tracking changes and troubleshooting issues. Drizzle ORM provides the .$onUpdate method specifically for this purpose: it ensures the timestamp is refreshed automatically on updates.

In the Better Auth codebase, the omission of .$onUpdate for updatedAt isn't documented or explained—it's likely just an oversight in the schema generator logic, not a deliberate design choice. The expectation to auto-update comes from general database conventions, not from anything specific in Better Auth or Drizzle ORM docs or code. If you want this behavior, you should manually add .$onUpdate(() => new Date()) to your schema field. source

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Aug 24, 2025):  It's considered best practice in most ORMs and relational databases to auto-update the `updatedAt` field whenever a record changes, especially for user/auth tables. This helps with auditability, debugging, and compliance—knowing when data was last modified is crucial for tracking changes and troubleshooting issues. Drizzle ORM provides the `.$onUpdate` method specifically for this purpose: it ensures the timestamp is refreshed automatically on updates. In the Better Auth codebase, the omission of `.$onUpdate` for `updatedAt` isn't documented or explained—it's likely just an oversight in the schema generator logic, not a deliberate design choice. The expectation to auto-update comes from general database conventions, not from anything specific in Better Auth or Drizzle ORM docs or code. If you want this behavior, you should manually add `.$onUpdate(() => new Date())` to your schema field. [source](https://github.com/better-auth/better-auth/blob/577cfb4ab3b16d22f36892c0e843f36abcee80c3/packages/cli/src/generators/drizzle.ts)  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/03a03352-37ce-488a-ad99-bc0e0273f2eb?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/03a03352-37ce-488a-ad99-bc0e0273f2eb?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/03a03352-37ce-488a-ad99-bc0e0273f2eb?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/03a03352-37ce-488a-ad99-bc0e0273f2eb?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/03a03352-37ce-488a-ad99-bc0e0273f2eb?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/03a03352-37ce-488a-ad99-bc0e0273f2eb?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/03a03352-37ce-488a-ad99-bc0e0273f2eb?feedback_type=other)</sup>  [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/4187)

GiteaMirror commented

2026-04-13 05:37:44 -05:00

@iamsg97 commented on GitHub (Aug 25, 2025):

Hello @yvbbrjdr 👋🏻
I am working to solve this, will share the branch details shortly. Then once the solution is ready, I might reach out to understand how to test it thoroughly.
Thanks in advance ✌🏻

@iamsg97 commented on GitHub (Aug 25, 2025): Hello @yvbbrjdr 👋🏻 I am working to solve this, will share the branch details shortly. Then once the solution is ready, I might reach out to understand how to test it thoroughly. Thanks in advance ✌🏻

GiteaMirror commented

2026-04-13 05:37:45 -05:00

@iamsg97 commented on GitHub (Aug 26, 2025):

Hello @yvbbrjdr, Happy Tuesday 👋🏻
Here is the change that I think should solve the issue. But I need some guidance on the tests.

What I am looking 👀 for 💭

I create a drizzle integration with better-auth (✅ this is fine)
It will be helpful if you can share me your auth config and schema.

Reason for the ask is it would save me some time, and I would make sure that I am not doing which is out of scope of this ticket 🥹

cc: @ping-maxwell @Kinfe123

@iamsg97 commented on GitHub (Aug 26, 2025): Hello @yvbbrjdr, Happy Tuesday 👋🏻 [Here](https://github.com/iamsg97/better-auth/commit/24dc130652fb3646c31019984ba5b5e7035d0515) is the change that I think should solve the issue. But I need some guidance on the tests. What I am looking 👀 for 💭 - I create a drizzle integration with better-auth (✅ this is fine) - It will be helpful if you can share me your auth config and schema. > Reason for the ask is it would save me some time, and I would make sure that I am not doing which is out of scope of this ticket 🥹 cc: @ping-maxwell @Kinfe123

GiteaMirror commented

2026-04-13 05:37:46 -05:00

@iamsg97 commented on GitHub (Aug 26, 2025):

Hello @yvbbrjdr 👋🏻
In continuation to the above, by any means do the config of yours look something similar. I was going through the better-auth docs, and I could make something like this (I am assuming, I might not be correct here)

import { createFieldAttribute } from "better-auth";

const options: BetterAuthOptions = {
  // keep other options as needed...
  user: {
    modelName: "user",
    // either put these in `additionalFields` or in a plugin schema; generator merges schemas.
    additionalFields: {
      // model property -> FieldAttribute
      name: createFieldAttribute("string", { required: true }),
      email: createFieldAttribute("string", { required: true, unique: true }),
      emailVerified: createFieldAttribute("boolean", {
        required: true,
        // make this a function so generator emits .$defaultFn(() => false)
        defaultValue: () => false,
      }),
      image: createFieldAttribute("string", { required: false }),
      createdAt: createFieldAttribute("date", {
        required: true,
        // function default produces .$defaultFn(() => /* @__PURE__ */ new Date())
        defaultValue: () => /* @__PURE__ */ new Date(),
      }),
      updatedAt: createFieldAttribute("date", {
        required: true,
        defaultValue: () => /* @__PURE__ */ new Date(),
        // explicit onUpdate isn't necessary because the generator infers onUpdate for fields named updated/updatedAt/updated_at,
        // but you can add a non-typed `onUpdate: true` or a function if desired.
        // onUpdate: true
      }),
    },
  },
};

If the above makes sense, all we need to add is a new property like below:

continuing from the above code comments

updatedAt: createFieldAttribute("date", {
        required: true,
        defaultValue: () => /* @__PURE__ */ new Date(),
        // explicit onUpdate isn't necessary because the generator infers onUpdate for fields named updated/updatedAt/updated_at,
        // but you can add a non-typed `onUpdate: true` or a function if desired.
        onUpdate: () => /* @__PURE__ */ new Date()
      })

@iamsg97 commented on GitHub (Aug 26, 2025): Hello @yvbbrjdr 👋🏻 In continuation to the above, by any means do the config of yours look something similar. I was going through the better-auth docs, and I could make something like this (I am assuming, I might not be correct here) ```ts import { createFieldAttribute } from "better-auth"; const options: BetterAuthOptions = { // keep other options as needed... user: { modelName: "user", // either put these in `additionalFields` or in a plugin schema; generator merges schemas. additionalFields: { // model property -> FieldAttribute name: createFieldAttribute("string", { required: true }), email: createFieldAttribute("string", { required: true, unique: true }), emailVerified: createFieldAttribute("boolean", { required: true, // make this a function so generator emits .$defaultFn(() => false) defaultValue: () => false, }), image: createFieldAttribute("string", { required: false }), createdAt: createFieldAttribute("date", { required: true, // function default produces .$defaultFn(() => /* @__PURE__ */ new Date()) defaultValue: () => /* @__PURE__ */ new Date(), }), updatedAt: createFieldAttribute("date", { required: true, defaultValue: () => /* @__PURE__ */ new Date(), // explicit onUpdate isn't necessary because the generator infers onUpdate for fields named updated/updatedAt/updated_at, // but you can add a non-typed `onUpdate: true` or a function if desired. // onUpdate: true }), }, }, }; ``` If the above makes sense, all we need to add is a new property like below: _continuing from the above code comments_ ```ts updatedAt: createFieldAttribute("date", { required: true, defaultValue: () => /* @__PURE__ */ new Date(), // explicit onUpdate isn't necessary because the generator infers onUpdate for fields named updated/updatedAt/updated_at, // but you can add a non-typed `onUpdate: true` or a function if desired. onUpdate: () => /* @__PURE__ */ new Date() }) ```

GiteaMirror commented

2026-04-13 05:37:47 -05:00

@himself65 commented on GitHub (Aug 26, 2025):

Hello @yvbbrjdr 👋🏻 In continuation to the above, by any means do the config of yours look something similar. I was going through the better-auth docs, and I could make something like this (I am assuming, I might not be correct here)

import { createFieldAttribute } from "better-auth";

const options: BetterAuthOptions = {
// keep other options as needed...
user: {
modelName: "user",
// either put these in additionalFields or in a plugin schema; generator merges schemas.
additionalFields: {
// model property -> FieldAttribute
name: createFieldAttribute("string", { required: true }),
email: createFieldAttribute("string", { required: true, unique: true }),
emailVerified: createFieldAttribute("boolean", {
required: true,
// make this a function so generator emits .$defaultFn(() => false)
defaultValue: () => false,
}),
image: createFieldAttribute("string", { required: false }),
createdAt: createFieldAttribute("date", {
required: true,
// function default produces .$defaultFn(() => /* @PURE / new Date())
defaultValue: () => / @PURE / new Date(),
}),
updatedAt: createFieldAttribute("date", {
required: true,
defaultValue: () => / @PURE */ new Date(),
// explicit onUpdate isn't necessary because the generator infers onUpdate for fields named updated/updatedAt/updated_at,
// but you can add a non-typed onUpdate: true or a function if desired.
// onUpdate: true
}),
},
},
};
If the above makes sense, all we need to add is a new property like below:

continuing from the above code comments

updatedAt: createFieldAttribute("date", {
required: true,
defaultValue: () => /* @PURE / new Date(),
// explicit onUpdate isn't necessary because the generator infers onUpdate for fields named updated/updatedAt/updated_at,
// but you can add a non-typed onUpdate: true or a function if desired.
onUpdate: () => / @PURE */ new Date()
})

Hi, just open the PR. I think you are going on the right path. Thanks

@himself65 commented on GitHub (Aug 26, 2025): > Hello [@yvbbrjdr](https://github.com/yvbbrjdr) 👋🏻 In continuation to the above, by any means do the config of yours look something similar. I was going through the better-auth docs, and I could make something like this (I am assuming, I might not be correct here) > > import { createFieldAttribute } from "better-auth"; > > const options: BetterAuthOptions = { > // keep other options as needed... > user: { > modelName: "user", > // either put these in `additionalFields` or in a plugin schema; generator merges schemas. > additionalFields: { > // model property -> FieldAttribute > name: createFieldAttribute("string", { required: true }), > email: createFieldAttribute("string", { required: true, unique: true }), > emailVerified: createFieldAttribute("boolean", { > required: true, > // make this a function so generator emits .$defaultFn(() => false) > defaultValue: () => false, > }), > image: createFieldAttribute("string", { required: false }), > createdAt: createFieldAttribute("date", { > required: true, > // function default produces .$defaultFn(() => /* @__PURE__ */ new Date()) > defaultValue: () => /* @__PURE__ */ new Date(), > }), > updatedAt: createFieldAttribute("date", { > required: true, > defaultValue: () => /* @__PURE__ */ new Date(), > // explicit onUpdate isn't necessary because the generator infers onUpdate for fields named updated/updatedAt/updated_at, > // but you can add a non-typed `onUpdate: true` or a function if desired. > // onUpdate: true > }), > }, > }, > }; > If the above makes sense, all we need to add is a new property like below: > > _continuing from the above code comments_ > > updatedAt: createFieldAttribute("date", { > required: true, > defaultValue: () => /* @__PURE__ */ new Date(), > // explicit onUpdate isn't necessary because the generator infers onUpdate for fields named updated/updatedAt/updated_at, > // but you can add a non-typed `onUpdate: true` or a function if desired. > onUpdate: () => /* @__PURE__ */ new Date() > }) Hi, just open the PR. I think you are going on the right path. Thanks

GiteaMirror commented

2026-04-13 05:37:48 -05:00

@himself65 commented on GitHub (Aug 26, 2025):

I'm opening the PR to add onUpdate option to schema

@himself65 commented on GitHub (Aug 26, 2025): I'm opening the PR to add `onUpdate` option to schema

GiteaMirror commented

2026-04-13 05:37:49 -05:00

@iamsg97 commented on GitHub (Aug 27, 2025):

Thanks! I think apart from the tests I am pretty much inclined with you on the solution.
I will go through the tests to understand it ✌🏻

@iamsg97 commented on GitHub (Aug 27, 2025): Thanks! I think apart from the `tests` I am pretty much inclined with you on the solution. I will go through the `tests` to understand it ✌🏻

GiteaMirror commented

2026-04-13 05:37:50 -05:00

@maelp commented on GitHub (Aug 27, 2025):

I don't have a createFieldAttribute export on better-auth? has it been removed?

@maelp commented on GitHub (Aug 27, 2025): I don't have a `createFieldAttribute` export on better-auth? has it been removed?

GiteaMirror commented

2026-04-13 05:37:51 -05:00

@iamsg97 commented on GitHub (Aug 28, 2025):

Hello @maelp greetings 👋🏻
I still do see that in the source code 🧑🏻‍💻

May be someone like @ping-maxwell @Kinfe123 from the org can help you with the details, about usage in the latest version!

@iamsg97 commented on GitHub (Aug 28, 2025): Hello @maelp greetings 👋🏻 I still do see that in the source code 🧑🏻‍💻 <img width="637" height="306" alt="Image" src="https://github.com/user-attachments/assets/09217fd0-f654-4a01-a403-4a130d4000c1" /> May be someone like @ping-maxwell @Kinfe123 from the org can help you with the details, about usage in the latest version!

GiteaMirror commented

2026-04-13 05:37:52 -05:00

@maelp commented on GitHub (Aug 28, 2025):

interesting weird, or perhaps it's on the latest version and I have the one before, because it wouldn't load for me, I'm using 1.3.7

@maelp commented on GitHub (Aug 28, 2025): interesting weird, or perhaps it's on the latest version and I have the one before, because it wouldn't load for me, I'm using 1.3.7 <img width="1724" height="238" alt="Image" src="https://github.com/user-attachments/assets/b82ef371-ba83-4273-80dd-1cb9f8cac916" />

Sign in to join this conversation.

Branches Tags

feat/oauth-provider-custom-subject

main

2026-05-29/fix/api-key-verify-unscoped-config

fix/oauth-callback-path-declarative

docs/oauth-provider-metadata-routing

dependabot/npm_and_yarn/demo/electron/demo-minor-patch-227a091249

dependabot/github_actions/github-actions-98f3470200

dependabot/npm_and_yarn/samlify-2.13.0

changeset-release/next

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-07/fix/admin-set-password-upsert

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-29/feat/google-include-granted-scopes

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

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-provider-backchannel-logout-next

feat/oauth-idp-initiated-bounce

refactor/sign-in-challenges

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

fix/release-notes-new-packages

fix/two-factor-identity-guard

fix/resource

feat/emailpassword-authorize

2026-04-12/security/dynamic-baseurl-proxy-trust-default

feat/oauth-provider-at-hash-v2

fix/release-grep-fallback

claude/address-review-comments-JhFLr

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

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-24/fix/update-user-info-on-link

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#9855

[GH-ISSUE #4187] $onUpdate is not set for updatedAt field in psql schema #9855

Is this suited for github?

To Reproduce

Current vs. Expected behavior

What version of Better Auth are you using?

System info

Which area(s) are affected? (Select all that apply)

Auth config (if applicable)

Additional context

[GH-ISSUE #4187] `$onUpdate` is not set for `updatedAt` field in psql schema #9855