@netlify/agent-runner-cli 1.94.0 → 1.96.0

package/dist/skills/netlify-db@netlifydb/SKILL.md

@@ -23,6 +23,18 @@ This affects:
 
 The `drizzle-kit` package is NOT affected — use the regular `drizzle-kit` package.
 
+## CRITICAL: Database schema changes always require migrations
+
+Any code change that assumes a different database schema (adding tables, adding columns, renaming fields, changing types,
+adding indexes, etc.) will only work if a corresponding migration exists in `netlify/db/migrations/`. Without a
+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/db` driver:
+- **With Drizzle ORM**: Update the schema definition, then run `npx drizzle-kit generate`
+- **With native driver**: Write a new SQL migration file in `netlify/db/migrations/`
+
+Never consider a schema change complete without a corresponding migration file.
+
 ## Setup with Drizzle ORM (recommended)
 
 This is the recommended approach. It gives you type-safe schema definitions, a query builder, and automatic migration
@@ -148,6 +160,17 @@ export const config: Config = {
 };
 ```
 
+### Modifying an existing schema
+
+When adding columns, tables, or changing the schema in an existing project:
+
+1. Update the Drizzle schema definition with your changes
+2. Run `npx drizzle-kit generate` — this is REQUIRED, not optional
+3. Verify new migration files appear in `netlify/db/migrations/`
+4. Update any application code that uses the changed tables
+
+Do NOT skip step 2. The database will not reflect your schema changes without a generated migration.
+
 ### Drizzle ORM query reference
 
 ```typescript
@@ -322,8 +345,10 @@ Drizzle Kit generates migrations in the subdirectory format. Both formats can co
 2. **Using `drizzle-orm` instead of `netlify-drizzle-orm-tests`**: The Netlify DB adapter is not yet in the main
    `drizzle-orm` package. Use `netlify-drizzle-orm-tests` for all Drizzle imports.
 
-3. **Forgetting to run `drizzle-kit generate`**: After changing `db/schema.ts`, you must run `npx drizzle-kit generate`
-   to create migration files. Schema changes alone do nothing — the migration files are what Netlify applies.
+3. **NEVER skip migration generation after schema changes**: Any code that assumes a different database schema requires
+   a corresponding migration in `netlify/db/migrations/`. With Drizzle ORM, run `npx drizzle-kit generate` after
+   updating the schema definition. With the native driver, write a SQL migration file. Schema changes alone do
+   nothing — the migration files are what Netlify applies. The application WILL break without them.
 
 4. **Editing generated migrations**: Never manually edit migrations created by Drizzle Kit. If you need to change
    something, update the schema and generate a new migration.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@netlify/agent-runner-cli",
   "type": "module",
-  "version": "1.94.0",
+  "version": "1.96.0",
   "description": "CLI tool for running Netlify agents",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
@@ -81,7 +81,7 @@
     "vitest": "^4.0.16"
   },
   "dependencies": {
-    "@anthropic-ai/claude-code": "2.1.81",
+    "@anthropic-ai/claude-code": "2.1.87",
     "@anthropic-ai/sdk": "0.78.0",
     "@google/gemini-cli": "0.31.0",
     "@netlify/otel": "^5.1.5",