@jaypie/mcp 0.6.4 → 0.6.6

package/dist/suites/docs/index.js

@@ -8,7 +8,7 @@ import { gt } from 'semver';
 /**
  * Docs Suite - Documentation services (skill, version, release_notes)
  */
-const BUILD_VERSION_STRING = "@jaypie/mcp@0.6.4#db054728"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.6.6#c35efb78"
     ;
 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.6.4",
+  "version": "0.6.6",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/constructs/1.2.23.md

@@ -0,0 +1,43 @@
+---
+version: 1.2.23
+date: 2025-01-26
+summary: Fix shared secrets not injecting env vars across constructs (Issue #158)
+---
+
+# @jaypie/constructs 1.2.23
+
+## Bug Fix
+
+### Shared Secrets Between Constructs (Issue #158)
+
+Fixed an issue where secrets declared in multiple constructs (e.g., `JaypieQueuedLambda` and `JaypieNextJs`) would not properly inject `SECRET_*` environment variables or grant IAM permissions to the second construct.
+
+**Root Cause**: `JaypieLambda` and `JaypieNextJs` were calling `resolveSecrets(scope, ...)` with their parent construct as the scope. This caused secrets to be cached per-construct rather than per-stack, so constructs couldn't share secrets.
+
+**Fix**: Changed both `JaypieLambda` and `JaypieNextJs` to use `Stack.of(this)` as the scope for `resolveSecrets`. This ensures:
+- Secrets are shared at the stack level across all constructs
+- Each construct sets its own `SECRET_*` environment variables
+- Each construct grants IAM permissions to its Lambda function
+
+**Before** (broken):
+```typescript
+// JaypieQueuedLambda created secrets under its own namespace
+// JaypieNextJs couldn't find or use those secrets
+const jobProcessor = new JaypieQueuedLambda(this, "JobProcessor", {
+  secrets: ["ANTHROPIC_API_KEY"],  // Created JobProcessorANTHROPICAPIKEY-xxx
+});
+const nextjsApp = new JaypieNextJs(this, "NextJsApp", {
+  secrets: ["ANTHROPIC_API_KEY"],  // Missing env var and permissions!
+});
+```
+
+**After** (fixed):
+```typescript
+// Both constructs share secrets at stack level
+const jobProcessor = new JaypieQueuedLambda(this, "JobProcessor", {
+  secrets: ["ANTHROPIC_API_KEY"],  // Creates shared secret
+});
+const nextjsApp = new JaypieNextJs(this, "NextJsApp", {
+  secrets: ["ANTHROPIC_API_KEY"],  // Reuses same secret, gets env var + permissions
+});
+```

package/release-notes/constructs/1.2.24.md

@@ -0,0 +1,15 @@
+---
+version: 1.2.24
+date: 2025-01-26
+summary: Fix JaypieNextJs Lambda timeout defaulting to 10 seconds instead of 900 seconds
+---
+
+## Bug Fix
+
+- **JaypieNextJs timeout**: Lambda functions deployed via `JaypieNextJs` now default to 900 seconds (`CDK.DURATION.LAMBDA_WORKER`) instead of the 10-second default from `cdk-nextjs-standalone`. This fix applies to both the server function and image optimization function.
+
+## Details
+
+Previously, the `JaypieNextJs` construct did not pass a `timeout` property to the underlying `cdk-nextjs-standalone` Nextjs construct, causing Lambda functions to timeout after just 10 seconds. This was inconsistent with other Jaypie Lambda constructs like `JaypieQueuedLambda` which correctly defaulted to 900 seconds.
+
+Fixes #162.

package/release-notes/jaypie/1.2.6.md

@@ -0,0 +1,10 @@
+---
+version: 1.2.6
+date: 2025-01-26
+summary: Update @jaypie/llm peer dependency to 1.2.8
+---
+
+## Dependencies
+
+- Updated `@jaypie/llm` peer dependency to ^1.2.8
+  - Includes fix for streaming crash after tool execution

package/release-notes/llm/1.2.8.md

@@ -0,0 +1,28 @@
+---
+version: 1.2.8
+date: 2025-01-26
+summary: Fix streaming crash after tool execution in Anthropic and OpenRouter adapters
+---
+
+## Bug Fixes
+
+- **Streaming with Tools**: Fixed crash in `Llm.stream()` when tools are executed
+  - Error: "Cannot read properties of undefined (reading 'map')"
+  - Root cause: FunctionCall/FunctionCallOutput messages lack role/content fields
+  - Fixed in AnthropicAdapter and OpenRouterAdapter buildRequest methods
+
+## Technical Details
+
+StreamLoop adds messages with `type: LlmMessageType.FunctionCall` and `type: LlmMessageType.FunctionCallOutput` to conversation history. These message types don't have `role` and `content` fields that adapters expected.
+
+### AnthropicAdapter Changes
+- FunctionCall messages converted to assistant message with `tool_use` block
+- FunctionCallOutput messages converted to user message with `tool_result` block
+
+### OpenRouterAdapter Changes
+- FunctionCall messages converted to assistant message with `toolCalls` array
+- FunctionCallOutput messages converted to `tool` role message
+
+## Related
+
+- Fixes GitHub Issue #165

package/release-notes/mcp/0.6.5.md

@@ -0,0 +1,12 @@
+---
+version: 0.6.5
+date: 2026-01-26
+summary: Added migration guide for class to category refactor in DynamoDB skill
+---
+
+# @jaypie/mcp 0.6.5
+
+## Changes
+
+- Added migration section to `dynamodb` skill documenting the `class` → `category` field rename in @jaypie/dynamodb 0.4.0+
+- Documents table recreation and migration script options for existing tables

package/skills/dynamodb.md

@@ -147,3 +147,19 @@ describe("OrderService", () => {
 });
 ```
 
+## Migration: class to category (v0.4.0)
+
+Version 0.4.0 renamed `class` → `category` and `indexClass` → `indexCategory`.
+
+**If your table was created with an older version:**
+
+1. **Local dev**: Delete and recreate the table using MCP `createTable`
+2. **Production**: See `packages/dynamodb/CLAUDE.md` for migration script
+
+| Old | New |
+|-----|-----|
+| `class` | `category` |
+| `indexClass` | `indexCategory` |
+| `INDEX_CLASS` | `INDEX_CATEGORY` |
+| `queryByClass()` | `queryByCategory()` |
+