@jaypie/mcp 0.8.2 → 0.8.4

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.2#6d5f241e"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.4#71fb4b1f"
     ;
 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.2",
+  "version": "0.8.4",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/logger/1.2.6.md

@@ -0,0 +1,10 @@
+---
+version: 1.2.6
+date: 2026-03-26
+summary: Export getDatadogTransport for clean shutdown in production
+---
+
+## Changes
+
+- Export `getDatadogTransport` from `@jaypie/logger` for production use cases like flushing the transport before `process.exit()` in ECS Fargate containers
+- Closes #248

package/release-notes/logger/1.2.7.md

@@ -0,0 +1,24 @@
+---
+version: 1.2.7
+date: 2026-03-27
+summary: Rename JSON log field from "log" to "level" to fix Datadog CloudWatch collision
+---
+
+## Changes
+
+- Renamed `"log"` field to `"level"` in JSON output to prevent Datadog Forwarder from interpreting the log level as the message content
+- Updated DatadogTransport to strip `"level"` instead of `"log"` when forwarding
+- Closes #250
+
+## Migration
+
+JSON output changes from:
+```json
+{"log":"debug","message":"hello"}
+```
+to:
+```json
+{"level":"debug","message":"hello"}
+```
+
+Any log parsing rules that match on the `"log"` field should be updated to match `"level"`.

package/release-notes/testkit/1.2.27.md

@@ -0,0 +1,9 @@
+---
+version: 1.2.27
+date: 2026-03-26
+summary: Add getDatadogTransport mock
+---
+
+## Changes
+
+- Added `getDatadogTransport` mock (returns `null`) matching new `@jaypie/logger` export

package/skills/logs.md

@@ -28,7 +28,7 @@ log.error("Error message");
 log.fatal("Fatal error"); // only used internally in jaypie
 ```
 
-## Logging Objects
+## Logging Data
 
 DO NOT use multiple parameters when logging:
 <BAD>
@@ -61,13 +61,15 @@ log.var({ Processing: {
 } });
 ```
 
+Log any important, even scalar, data and filter with `var` in Datadog
+
 ## Setting Log Level
 
 Via environment variable:
 
 ```bash
 LOG_LEVEL=debug npm run dev
-LOG_LEVEL=trace npm test
+LOG_LEVEL=trace MODULE_LOG_LEVEL=warn npm test
 ```
 
 ## Lambda Logging