Gustavo Valverde
834841fbc9
Brings main's `chore: release v1.6.3 (#9081)` commit into next after the stable release. Conflict resolution: - `packages/*/package.json`: keep next's `1.7.0-beta.0` (per the release bot's standard rule: next is always ahead of main in version). - `packages/*/CHANGELOG.md`: keep both version entries side-by-side. Next's `1.7.0-beta.0` section stays on top; main's new `1.6.3` section slots in below. Each entry describes its own branch's release. - `.changeset/*.md`: restore the 14 changesets git auto-deleted. Next is in pre-release mode (`.changeset/pre.json` `mode: "pre"`), so changesets accumulate across beta cuts and are only consumed on `exit-pre`. Main's release deleted them from main; next must keep them for its own pre-release accumulator.
Better Auth CLI
Better Auth comes with a built-in CLI to help you manage the database schema needed for both core functionality and plugins.
Init
The CLI includes an init command to add Better Auth to your project.
npx auth@latest init
Generate
The generate command creates the schema required by Better Auth.
If you’re using a database adapter like Prisma or Drizzle, this command will
generate the right schema for your ORM.
If you’re using the built-in Kysely adapter, it will generate an SQL file you
can run directly on your database.
npx auth@latest generate
Migrate
The migrate command applies the Better Auth schema directly to your database.
This is available if you’re using the built-in Kysely adapter.
For other adapters, you’ll need to apply the schema using your ORM’s migration
tool.
npx auth@latest migrate
Secret
The CLI also provides a way to generate a secret key for your Better Auth instance.
npx auth@latest secret
License
MIT