@beignet/provider-db-drizzle 0.0.31 → 0.0.32

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @beignet/provider-db-drizzle
 
+## 0.0.32
+
+### Patch Changes
+
+- f759611: README and the shipped database-provider skill now reference
+  `beignet db schema sync`, the renamed form of `db schema generate`.
+
 ## 0.0.31
 
 ## 0.0.30

package/README.md

@@ -110,7 +110,7 @@ idempotency, or outbox, generate the provider-owned table exports into the app
 schema:
 
 ```bash
-bun beignet db schema generate
+bun beignet db schema sync
 ```
 
 That writes `infra/db/schema/beignet.ts` and adds
@@ -1118,7 +1118,7 @@ Each backend also exports canonical Beignet operational table definitions:
 - `@beignet/provider-db-drizzle/mysql/schema`
 
 Each schema subpath exports `auditLog`, `idempotencyRecords`, and
-`outboxMessages`. Prefer `beignet db schema generate` in apps so the selected
+`outboxMessages`. Prefer `beignet db schema sync` in apps so the selected
 exports are re-exported from your app schema index before Drizzle Kit generates
 migrations.
 

package/package.json

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

package/skills/database-provider/SKILL.md

@@ -40,7 +40,7 @@ When audit, idempotency, or outbox need provider-owned SQL tables, generate the
 Beignet table exports into the app schema, then run the normal migration flow:
 
 ```bash
-beignet db schema generate
+beignet db schema sync
 beignet db generate
 beignet db migrate
 ```