@jaypie/mcp 0.8.88 → 0.8.89

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.8.88#f5108b78"
12
+ const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.89#aa6c226c"
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.8.88",
3
+ "version": "0.8.89",
4
4
  "description": "Jaypie MCP",
5
5
  "repository": {
6
6
  "type": "git",
@@ -0,0 +1,28 @@
1
+ ---
2
+ version: 1.2.27
3
+ date: 2026-07-03
4
+ summary: Express 5 support — dual-compatible EXPRESS.PATH.ANY, optional express peer, dev harness on Express 5
5
+ ---
6
+
7
+ # @jaypie/express 1.2.27
8
+
9
+ ## Features
10
+
11
+ - **Express 5 support**: The package is now developed and tested against Express `^5.1.0`. Express is type-only at runtime, so both Express 4 and Express 5 apps are supported.
12
+ - **Optional peer dependency**: Declares `express >=4.0.0` as an optional peer dependency to document the supported range.
13
+
14
+ ## Changes
15
+
16
+ - **`EXPRESS.PATH.ANY` is now a RegExp**: Previously `"*"`, which throws at route registration under Express 5 (path-to-regexp 8 requires named wildcards). The constant is now a RegExp that matches all paths in both Express 4 and Express 5. Code such as `app.all(EXPRESS.PATH.ANY, notFoundRoute)` continues to work unchanged on either major.
17
+
18
+ ## Technical Details
19
+
20
+ - All runtime `req`/`res` API usage (`res.status().json()`, `res.send()`, `res.set()`, `res.vary()`, read-only `req.query`) is identical across Express 4 and 5.
21
+ - The Lambda adapter (`LambdaRequest`, `LambdaResponseBuffered`, `LambdaResponseStreaming`) is validated against Express 5 internals via the adapter integration suite and docker harness.
22
+ - Supertest coverage added for the `app.all(EXPRESS.PATH.ANY, ...)` catch-all pattern.
23
+
24
+ ## Migration
25
+
26
+ - No action required for Express 4 clients.
27
+ - Express 5 clients should not use bare `"*"` route paths (an Express 5 restriction); `EXPRESS.PATH.ANY` now works on both majors.
28
+ - Code depending on `EXPRESS.PATH.ANY` being the literal string `"*"` (e.g., string comparison) must compare against the RegExp instead.
@@ -0,0 +1,12 @@
1
+ ---
2
+ version: 1.2.60
3
+ date: 2026-07-03
4
+ summary: Bump @jaypie/express to ^1.2.27 with Express 5 support
5
+ ---
6
+
7
+ ## Dependencies
8
+
9
+ - Bump `@jaypie/express` to `^1.2.27` — the package is now developed and
10
+ tested against Express 5 while remaining compatible with Express 4, and
11
+ `EXPRESS.PATH.ANY` is a RegExp valid on both majors (bare `"*"` route
12
+ paths throw on Express 5).
@@ -0,0 +1,10 @@
1
+ ---
2
+ version: 0.8.89
3
+ date: 2026-07-03
4
+ summary: Publish release notes for @jaypie/express 1.2.27, @jaypie/testkit 1.2.50, and jaypie 1.2.60
5
+ ---
6
+
7
+ ## Changes
8
+
9
+ - Add release notes for `@jaypie/express` 1.2.27 (Express 5 support),
10
+ `@jaypie/testkit` 1.2.50, and `jaypie` 1.2.60.
@@ -0,0 +1,11 @@
1
+ ---
2
+ version: 1.2.50
3
+ date: 2026-07-03
4
+ summary: Develop and test against Express 5
5
+ ---
6
+
7
+ # @jaypie/testkit 1.2.50
8
+
9
+ ## Changes
10
+
11
+ - **Express 5 dev dependency**: Supertest coverage of the `expressHandler` mock now runs against Express `^5.1.0`, certifying testkit mocks under Express 5. No runtime or API changes.