mirror of
https://github.com/stack-auth/stack.git
synced 2026-07-20 21:29:36 +08:00
b0367ca48d
Some checks failed
DB migration compat / Check if migrations changed (push) Has been cancelled
DB migration compat / Back-compat — Current branch migrations with ${{ needs.check-migrations-changed.outputs.base_branch }} branch code (push) Has been cancelled
DB migration compat / Forward-compat — Current branch code with ${{ needs.check-migrations-changed.outputs.base_branch }} branch migrations (push) Has been cancelled
DB migration compat / No migration changes (skipped) (push) Has been cancelled
The Subscription timestamp columns are timezone-less and the app always writes them as UTC, but bare NOW() is a timestamptz, so LEAST() and the assignment would go through implicit session-timezone casts — on a non-UTC session the capped-at-now branch would store a value shifted by the offset. NOW() AT TIME ZONE 'UTC' stays in the naive-UTC domain throughout. The tests now keep every timestamp comparison server-side in that same domain (lower bound from the row's own createdAt instead of a JS-captured clock): the driver's Date parse/serialize is tz-offset-asymmetric for timezone-less columns, and the JS clock can't be assumed to agree with the DB server clock. |
||
|---|---|---|
| .. | ||
| prisma | ||
| scripts | ||
| src | ||
| .env | ||
| .env.development | ||
| .eslintrc.cjs | ||
| .gitignore | ||
| instrumentation-client.ts | ||
| LICENSE | ||
| next.config.mjs | ||
| package.json | ||
| prisma.config.ts | ||
| tsconfig.json | ||
| vercel.json | ||
| vitest.config.ts | ||
| vitest.setup.ts | ||