@jaypie/mcp 0.6.5 → 0.6.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -8,7 +8,7 @@ import { gt } from 'semver';
|
|
|
8
8
|
/**
|
|
9
9
|
* Docs Suite - Documentation services (skill, version, release_notes)
|
|
10
10
|
*/
|
|
11
|
-
const BUILD_VERSION_STRING = "@jaypie/mcp@0.6.
|
|
11
|
+
const BUILD_VERSION_STRING = "@jaypie/mcp@0.6.6#c35efb78"
|
|
12
12
|
;
|
|
13
13
|
const __filename$1 = fileURLToPath(import.meta.url);
|
|
14
14
|
const __dirname$1 = path.dirname(__filename$1);
|
package/package.json
CHANGED
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
---
|
|
2
|
+
version: 1.2.24
|
|
3
|
+
date: 2025-01-26
|
|
4
|
+
summary: Fix JaypieNextJs Lambda timeout defaulting to 10 seconds instead of 900 seconds
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Bug Fix
|
|
8
|
+
|
|
9
|
+
- **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.
|
|
10
|
+
|
|
11
|
+
## Details
|
|
12
|
+
|
|
13
|
+
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.
|
|
14
|
+
|
|
15
|
+
Fixes #162.
|
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
---
|
|
2
|
+
version: 1.2.8
|
|
3
|
+
date: 2025-01-26
|
|
4
|
+
summary: Fix streaming crash after tool execution in Anthropic and OpenRouter adapters
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Bug Fixes
|
|
8
|
+
|
|
9
|
+
- **Streaming with Tools**: Fixed crash in `Llm.stream()` when tools are executed
|
|
10
|
+
- Error: "Cannot read properties of undefined (reading 'map')"
|
|
11
|
+
- Root cause: FunctionCall/FunctionCallOutput messages lack role/content fields
|
|
12
|
+
- Fixed in AnthropicAdapter and OpenRouterAdapter buildRequest methods
|
|
13
|
+
|
|
14
|
+
## Technical Details
|
|
15
|
+
|
|
16
|
+
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.
|
|
17
|
+
|
|
18
|
+
### AnthropicAdapter Changes
|
|
19
|
+
- FunctionCall messages converted to assistant message with `tool_use` block
|
|
20
|
+
- FunctionCallOutput messages converted to user message with `tool_result` block
|
|
21
|
+
|
|
22
|
+
### OpenRouterAdapter Changes
|
|
23
|
+
- FunctionCall messages converted to assistant message with `toolCalls` array
|
|
24
|
+
- FunctionCallOutput messages converted to `tool` role message
|
|
25
|
+
|
|
26
|
+
## Related
|
|
27
|
+
|
|
28
|
+
- Fixes GitHub Issue #165
|