Skip to content

refactor(schema): remove unused verification_tokens table#81

Merged
aqib-rx merged 1 commit into
feat/unified-schema-pipelinefrom
feat/ui-schema-dual-write
Jun 4, 2026
Merged

refactor(schema): remove unused verification_tokens table#81
aqib-rx merged 1 commit into
feat/unified-schema-pipelinefrom
feat/ui-schema-dual-write

Conversation

@aqib-rx
Copy link
Copy Markdown
Collaborator

@aqib-rx aqib-rx commented Jun 4, 2026

verification_tokens was a leftover from the retired Auth.js/NextAuth integration — nothing reads or writes it (the only DB op was a cleanup of expired rows). Email verification uses email_verification_tokens; resets use password_reset_tokens. Removed from the 3 dialect schema defs + aggregator, CORE_TABLE_NAMES, the PG re-export, the dialect bundles, the SQLite core DDL, the runtime cleanup-delete, the auth types, and the test fixtures/snapshot.

New installs no longer create it; existing DBs keep the empty table until a reset (optional: DROP TABLE IF EXISTS verification_tokens).

Summary

Type of change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would change existing behavior)
  • Documentation update
  • Refactor / chore (no user-facing change)

Related issues

Changeset

This repo uses Changesets. If your PR changes any publishable package under packages/*, you must include a changeset:

pnpm changeset

Then commit the generated .changeset/*.md file.

  • I added a changeset (or this PR only touches non-publishable code: docs, tests, internal tooling, apps/*)
  • I selected the correct semver bump (patch / minor / major)

The changeset-check CI job will fail if a publishable package is modified without a changeset.

Test plan

  • pnpm lint
  • pnpm check-types
  • pnpm build
  • Manually verified the change

Checklist

  • I read CONTRIBUTING (if it exists)
  • My commits follow the Conventional Commits spec (enforced by commitlint)
  • I targeted the main branch
  • I updated relevant documentation

Screenshots / recordings

Notes for reviewers

verification_tokens was a leftover from the retired Auth.js/NextAuth
integration — nothing reads or writes it (the only DB op was a cleanup of
expired rows). Email verification uses email_verification_tokens; resets use
password_reset_tokens. Removed from the 3 dialect schema defs + aggregator,
CORE_TABLE_NAMES, the PG re-export, the dialect bundles, the SQLite core DDL,
the runtime cleanup-delete, the auth types, and the test fixtures/snapshot.

New installs no longer create it; existing DBs keep the empty table until a
reset (optional: DROP TABLE IF EXISTS verification_tokens).
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 4, 2026

PR title fails Conventional Commits check

Unknown scope "schema" found in pull request title "refactor(schema): remove unused verification_tokens table". Scope must match one of: nextly, admin, client, ui, adapter-postgres, adapter-mysql, adapter-sqlite, adapter-drizzle, storage-s3, storage-vercel-blob, storage-uploadthing, plugin-form-builder, create-nextly-app, eslint-config, prettier-config, tsconfig, playground, root, ci, docs, deps, release.

Examples of valid titles:

  • feat(admin): add role manager dialog
  • fix(adapter-postgres): handle connection pool exhaustion
  • chore(deps): bump zod to 4.2.0

@github-actions github-actions Bot added the scope: core nextly label Jun 4, 2026
@aqib-rx aqib-rx merged commit adc3114 into feat/unified-schema-pipeline Jun 4, 2026
1 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant