@beignet/provider-db-drizzle 0.0.9 → 0.0.10

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @beignet/provider-db-drizzle
 
+## 0.0.10
+
+### Patch Changes
+
+- 2972ee4: `beignet create` supports `--db sqlite|postgres|mysql` (default `sqlite`), with a matching database prompt in interactive setup. Each backend scaffolds end to end: provider wiring, an idiomatic Drizzle schema, the vendored initial migration, env examples (`POSTGRES_DB_URL`, `MYSQL_DB_URL`), and a dialect-matched test database — in-memory libSQL for SQLite, in-process PGlite for Postgres, and a real server via `MYSQL_TEST_URL` for MySQL. `make resource` and `make feature` detect the app's database and generate dialect-correct schema and repository code, and `beignet db generate|migrate` work unchanged for every dialect.
+
 ## 0.0.9
 
 ### Patch Changes

package/README.md

@@ -42,9 +42,9 @@ install, the subpath import, and the connection env var. Contracts, use cases,
 policies, and routes keep depending on ports; only the infra adapter changes.
 
 The walkthrough below uses SQLite. The [Postgres](#postgres) and
-[MySQL](#mysql) sections cover what changes per backend. The CLI starter
-scaffolds SQLite; switching to Postgres or MySQL is manual wiring this
-release.
+[MySQL](#mysql) sections cover what changes per backend. The CLI scaffolds
+any of the three: `bun create beignet my-app --db sqlite|postgres|mysql`
+(default `sqlite`).
 
 ## Install
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@beignet/provider-db-drizzle",
-  "version": "0.0.9",
+  "version": "0.0.10",
   "type": "module",
   "description": "Drizzle ORM database providers for Beignet — typed DbPort, unit of work, outbox, and idempotency for SQLite (libSQL/Turso), Postgres, and MySQL.",
   "exports": {