@jaypie/mcp 0.7.23 → 0.7.25

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.23#49c71f6f"
12
+ const BUILD_VERSION_STRING = "@jaypie/mcp@0.7.25#23fde271"
13
13
  ;
14
14
  const __filename$1 = fileURLToPath(import.meta.url);
15
15
  const __dirname$1 = path.dirname(__filename$1);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jaypie/mcp",
3
- "version": "0.7.23",
3
+ "version": "0.7.25",
4
4
  "description": "Jaypie MCP",
5
5
  "repository": {
6
6
  "type": "git",
@@ -0,0 +1,12 @@
1
+ ---
2
+ version: 1.2.11
3
+ date: 2026-02-20
4
+ summary: Fix stale socket error crashing process during retry
5
+ ---
6
+
7
+ ## Changes
8
+
9
+ - Add `AbortController` per retry attempt in `RetryExecutor` and `StreamLoop` to kill lingering socket callbacks from dropped connections
10
+ - Add optional `signal?: AbortSignal` parameter to `executeRequest()` and `executeStreamRequest()` in `ProviderAdapter` interface
11
+ - `OpenRouterAdapter` forwards abort signal to the SDK, enabling clean cancellation on retry
12
+ - Prevents unhandled promise rejections from async socket teardown events during retry sleep
@@ -0,0 +1,12 @@
1
+ ---
2
+ version: 1.2.3
3
+ date: 2026-02-20
4
+ summary: Fix DatadogLogTransport message field conflict with Datadog pipeline remapper
5
+ ---
6
+
7
+ ## Changes
8
+
9
+ - Fix `DatadogLogTransport.send()` to parse JSON strings and extract `message` as the Datadog message field
10
+ - Exclude `log` field from entries — level is already captured in `status`, and the `log` field conflicted with Datadog's pipeline remapper overwriting message content
11
+ - Spread extra structured fields (tags, data, etc.) as top-level Datadog entry attributes instead of double-serializing
12
+ - Non-JSON strings and JSON without a `message` field fall back to using the raw string