@jaypie/mcp 0.8.139 → 0.8.140

package/dist/suites/docs/index.js

@@ -9,7 +9,7 @@ import { gt } from 'semver';
 /**
  * Docs Suite - Documentation services (skill, version, release_notes)
  */
-const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.139#b5c90690"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.140#19ea447a"
     ;
 const __filename$1 = fileURLToPath(import.meta.url);
 const __dirname$1 = path.dirname(__filename$1);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jaypie/mcp",
-  "version": "0.8.139",
+  "version": "0.8.140",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/jaypie/1.2.91.md

@@ -0,0 +1,11 @@
+---
+version: 1.2.91
+date: 2026-08-27
+summary: Pulls @jaypie/lambda 1.2.15 (migrationHandler pending poll fix)
+---
+
+# jaypie 1.2.91
+
+## Changed
+
+- Depends on `@jaypie/lambda` 1.2.15.

package/release-notes/lambda/1.2.15.md

@@ -0,0 +1,31 @@
+---
+version: 1.2.15
+date: 2026-08-27
+summary: migrationHandler omits Data on pending polls and skips migrations on Delete
+---
+
+## Changes
+
+- `migrationHandler` returns `{ IsComplete: false }` with no `Data` while a migration is pending.
+- Completed polls return `{ Data: result, IsComplete: true }`, and omit `Data` when the handler result is not a plain object.
+- `RequestType: "Delete"` short-circuits without invoking the migration: `onEvent` returns `PhysicalResourceId`, `isComplete` returns `{ IsComplete: true }`.
+
+## Motivation
+
+The `cr.Provider` framework throws `"Data" is not allowed if "IsComplete" is "False"`
+when a pending `isComplete` response carries any `Data` keys. Any migration set needing
+more than one invocation therefore failed the custom resource on the first pending poll,
+marking the resource `CREATE_FAILED`. The rollback then invoked the same handler for the
+`Delete` request, ran the next pending migration, failed the same way, and left the stack
+`ROLLBACK_FAILED`.
+
+Scalar and array results were also submitted as `Data`, which CloudFormation rejects
+because `Data` must be a map.
+
+## Migration
+
+No changes required. Handlers returning `{ pending: true }` now poll correctly. Handlers
+returning a scalar or array no longer expose that value through `Fn::GetAtt`; return a
+plain object to keep resource attributes.
+
+Fixes #510.

package/release-notes/mcp/0.8.140.md

@@ -0,0 +1,12 @@
+---
+version: 0.8.140
+date: 2026-08-27
+summary: Migrations skill documents the isComplete Data protocol and Delete short-circuit
+---
+
+## Changes
+
+- `skill("migrations")` records that pending polls carry no `Data`, that completion
+  returns `Data` only for plain-object results, and that `Delete` requests skip the
+  migration.
+- Release notes for `@jaypie/lambda` 1.2.15 and `jaypie` 1.2.91.

package/skills/migrations.md

@@ -45,7 +45,7 @@ new JaypieMigration(this, "SeedData", {
 
 - **Timeout**: 15 minutes per invocation (Lambda max); `totalTimeout` controls the end-to-end ceiling across all polling invocations (default 2 hours)
 - **Role**: Tagged as `CDK.ROLE.PROCESSING`
-- **Execution**: Uses `cr.Provider` with both `onEventHandler` and `isCompleteHandler` pointing to the same Lambda. The `onEventHandler` returns `PhysicalResourceId` immediately; the migration code runs in `isCompleteHandler` invocations, which are polled by Step Functions until `IsComplete: true`.
+- **Execution**: Uses `cr.Provider` with both `onEventHandler` and `isCompleteHandler` pointing to the same Lambda. The `onEventHandler` returns `PhysicalResourceId` immediately; the migration code runs in `isCompleteHandler` invocations, which are polled by Step Functions until `IsComplete: true`. `Delete` requests skip the migration entirely.
 - **Dependencies**: Use `dependencies` to ensure tables and other resources exist before the migration executes
 - **Permissions**: Tables passed via `tables` get data-plane (`grantReadWriteData`) plus control-plane access (`DescribeTable`, `UpdateTable`, `UpdateTimeToLive`, `UpdateContinuousBackups`) scoped to the table ARN and its indexes — migrations that add GSIs, toggle TTL, or change backups work without extra IAM
 
@@ -85,7 +85,20 @@ export const handler = migrationHandler(async (event) => {
 
 `migrationHandler` maps the `pending` flag onto CFN's `IsComplete` protocol:
 - `pending: true` → `{ IsComplete: false }` — waiter re-invokes after `queryInterval`
-- `pending: false` or omitted → `{ IsComplete: true }` — deploy proceeds
+- `pending: false` or omitted → `{ IsComplete: true, Data: result }` — deploy proceeds
+
+Pending responses carry no `Data`. The `cr.Provider` framework rejects
+`Data` alongside `IsComplete: false` with `"Data" is not allowed if "IsComplete" is "False"`,
+which fails the custom resource on the first pending poll. On completion the handler
+result is returned as `Data` only when it is a plain object; scalar and array results
+are reported complete without `Data` because CloudFormation accepts a map only.
+
+### Delete requests
+
+`migrationHandler` short-circuits `RequestType: "Delete"` without invoking the migration
+code. The resource being migrated is usually torn down in the same operation, so running
+migrations against it is wasted work, and a failure there strands the stack in
+`ROLLBACK_FAILED`.
 
 ## Building Migration Code