@jaypie/mcp 0.7.12 → 0.7.14
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.
|
@@ -9,7 +9,7 @@ import { gt } from 'semver';
|
|
|
9
9
|
/**
|
|
10
10
|
* Docs Suite - Documentation services (skill, version, release_notes)
|
|
11
11
|
*/
|
|
12
|
-
const BUILD_VERSION_STRING = "@jaypie/mcp@0.7.
|
|
12
|
+
const BUILD_VERSION_STRING = "@jaypie/mcp@0.7.14#00cead11"
|
|
13
13
|
;
|
|
14
14
|
const __filename$1 = fileURLToPath(import.meta.url);
|
|
15
15
|
const __dirname$1 = path.dirname(__filename$1);
|
package/package.json
CHANGED
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
---
|
|
2
|
+
version: 1.2.29
|
|
3
|
+
date: 2026-02-04
|
|
4
|
+
summary: CloudFront invalidation permission and SSM access for SSO
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# @jaypie/constructs 1.2.29
|
|
8
|
+
|
|
9
|
+
## Bug Fixes
|
|
10
|
+
|
|
11
|
+
- **JaypieWebDeploymentBucket**: Deploy role now includes `cloudfront:CreateInvalidation` permission when a CloudFront distribution is created, enabling GitHub Actions workflows to invalidate cache after deploying content
|
|
12
|
+
|
|
13
|
+
## Features
|
|
14
|
+
|
|
15
|
+
- **JaypieSsoPermissions**: Added `ssm:*` to developer permission set for Systems Manager access
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
---
|
|
2
|
+
version: 1.2.12
|
|
3
|
+
date: 2026-02-05
|
|
4
|
+
summary: Fix non-streaming expressHandler endpoints hanging in Lambda streaming mode
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Fixes
|
|
8
|
+
|
|
9
|
+
- **Lambda Streaming**: Fixed `expressHandler` endpoints that return data (non-streaming) hanging when used with `createLambdaStreamHandler`. The issue was that `safeSendJson()` called `flushHeaders()` before setting `content-type`, causing the JSON response to never be properly delivered to Lambda's response stream.
|
|
10
|
+
|
|
11
|
+
## Technical Details
|
|
12
|
+
|
|
13
|
+
The fix ensures proper order of operations for Lambda streaming responses:
|
|
14
|
+
1. Set status code
|
|
15
|
+
2. Set `content-type: application/json` header
|
|
16
|
+
3. Flush headers to initialize the Lambda stream wrapper
|
|
17
|
+
4. Write JSON data directly via `res.end()` instead of `res.json()`
|
|
18
|
+
|
|
19
|
+
This allows applications to use both streaming (SSE) and non-streaming (REST API) endpoints in the same Express app with `createLambdaStreamHandler`.
|
|
20
|
+
|
|
21
|
+
Fixes #187
|