@netlify/agent-runner-cli 1.145.0-test.3 → 1.145.0

package/dist/skills/netlify-database/SKILL.md

@@ -33,7 +33,7 @@ adding indexes, etc.) will only work if a corresponding migration exists in `net
 migration, the database schema will not change and the application will break at runtime.
 
 This applies regardless of whether you are using Drizzle ORM or the native `@netlify/database` driver:
-- **With Drizzle ORM**: Update the schema definition, then run `npx drizzle-kit generate --name <descriptive_name>`
+- **With Drizzle ORM**: Update the schema definition, then run `npx drizzle-kit generate`
 - **With native driver**: Write a new SQL migration file in `netlify/database/migrations/`
 
 Never consider a schema change complete without a corresponding migration file.
@@ -113,15 +113,12 @@ export default defineConfig({
 
 ### Step 5: Generate migrations
 
-Every time you change the schema, run `drizzle-kit generate` with a `--name` describing the change
-(max 50 characters, snake_case, starting with an imperative verb like add, create, drop, alter, rename, index):
+Every time you change the schema, run `drizzle-kit generate`:
 
 ```bash
-npx drizzle-kit generate --name add_users_bio
+npx drizzle-kit generate
 ```
 
-Without `--name`, drizzle-kit assigns a random two-word name that says nothing about the migration.
-
 This creates SQL migration files in `netlify/database/migrations/`.
 
 ### Step 6: Use the database in functions
@@ -357,7 +354,7 @@ applied to the database yet.
   as immutable. Roll forward with a new migration that applies the correction. This is always safe.
 - If a migration is **not yet applied** anywhere (it's only on disk), don't edit it in place. Run
   `netlify db migrations reset` to delete it, update `db/schema.ts` to reflect your new intent, then run
-  `npx drizzle-kit generate --name <descriptive_name>` to produce a fresh migration. Editing SQL or snapshot files directly can
+  `npx drizzle-kit generate` to produce a fresh migration. Editing SQL or snapshot files directly can
   desync Drizzle Kit's internal state and produce broken migrations on the next generate.
 
 ### `netlify db migrations reset` — cleaning up unapplied migrations

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@netlify/agent-runner-cli",
   "type": "module",
-  "version": "1.145.0-test.3",
+  "version": "1.145.0",
   "description": "CLI tool for running Netlify agents",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",