@jaypie/mcp 0.8.22 → 0.8.23
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.
|
|
12
|
+
const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.23#3db47ebf"
|
|
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.
|
|
3
|
+
"version": "0.8.23",
|
|
4
4
|
"description": "Jaypie MCP",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
@@ -39,7 +39,7 @@
|
|
|
39
39
|
"typecheck": "tsc --noEmit"
|
|
40
40
|
},
|
|
41
41
|
"dependencies": {
|
|
42
|
-
"@jaypie/fabric": "^0.2.
|
|
42
|
+
"@jaypie/fabric": "^0.2.4",
|
|
43
43
|
"@jaypie/tildeskill": "^0.2.0",
|
|
44
44
|
"@modelcontextprotocol/sdk": "^1.17.0",
|
|
45
45
|
"commander": "^14.0.0",
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
---
|
|
2
|
+
version: 0.4.4
|
|
3
|
+
date: 2026-04-10
|
|
4
|
+
summary: Pick up @jaypie/fabric@0.2.4 — query() once again falls back to DEFAULT_INDEXES for unregistered models
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# @jaypie/dynamodb 0.4.4
|
|
8
|
+
|
|
9
|
+
## Changes
|
|
10
|
+
|
|
11
|
+
- Picks up `@jaypie/fabric@0.2.4`, restoring the deprecated `DEFAULT_INDEXES` fallback inside `getModelIndexes()`
|
|
12
|
+
- `query({ model, scope })` against an unregistered model no longer throws `ConfigurationError`; it auto-detects `indexScope` from the restored `DEFAULT_INDEXES`
|
|
13
|
+
|
|
14
|
+
## Why
|
|
15
|
+
|
|
16
|
+
The 0.4.3 behavior surfaced as `ValidationException`/`ConfigurationError` against tables that previously worked, breaking deployed services. The fallback is restored as a deprecated behavior; both the dynamodb fallback and the underlying `@jaypie/fabric` `DEFAULT_INDEXES` export are slated for removal alongside `@jaypie/fabric@0.3.0`.
|
|
17
|
+
|
|
18
|
+
## Migration
|
|
19
|
+
|
|
20
|
+
Register model indexes explicitly with `registerModel({ model, indexes })` to be ready for the upcoming removal.
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
---
|
|
2
|
+
version: 0.2.4
|
|
3
|
+
date: 2026-04-10
|
|
4
|
+
summary: Restore DEFAULT_INDEXES export and getModelIndexes fallback removed in 0.2.3; both are deprecated and slated for removal in 0.3.0
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# @jaypie/fabric 0.2.4
|
|
8
|
+
|
|
9
|
+
## Restored
|
|
10
|
+
|
|
11
|
+
- `DEFAULT_INDEXES` export from `@jaypie/fabric` and `@jaypie/fabric/index` (removed in 0.2.3 via the same PR that added default security headers to `JaypieDistribution`)
|
|
12
|
+
- `getModelIndexes(model)` once again falls back to `DEFAULT_INDEXES` when a model has not been registered, restoring previous DynamoDB GSI behavior for unregistered models
|
|
13
|
+
|
|
14
|
+
## Why
|
|
15
|
+
|
|
16
|
+
The 0.2.3 removal was a breaking change that left downstream consumers without a way to populate GSI keys for unregistered models, surfacing as `ValidationException` errors against tables that previously worked.
|
|
17
|
+
|
|
18
|
+
## Deprecation
|
|
19
|
+
|
|
20
|
+
Both `DEFAULT_INDEXES` and the implicit fallback inside `getModelIndexes()` are marked `@deprecated`. They are scheduled for removal in 0.3.0. Register model indexes explicitly with `registerModel({ model, indexes })`.
|