@jaypie/mcp 0.8.52 → 0.8.53
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.53#ce234537"
|
|
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,20 @@
|
|
|
1
|
+
---
|
|
2
|
+
version: 0.6.1
|
|
3
|
+
date: 2026-05-02
|
|
4
|
+
summary: Auto-serialize Date instances to ISO 8601 strings on write so entities with Date-typed fields no longer crash the marshaller
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Fixed
|
|
8
|
+
|
|
9
|
+
- **Date values on entities**. `createEntity`, `updateEntity`, `deleteEntity`,
|
|
10
|
+
`archiveEntity`, `transactWriteEntities`, and `seedEntities` would throw
|
|
11
|
+
`Unsupported type passed: ...` from `@aws-sdk/util-dynamodb` whenever a
|
|
12
|
+
field held a `Date` instance — even though Jaypie entity timestamp types
|
|
13
|
+
are typed `Date | null`. The fix: `indexEntity` now walks the entity (top
|
|
14
|
+
level, nested objects, arrays) and converts any `Date` to
|
|
15
|
+
`value.toISOString()` before timestamps and GSI keys are populated.
|
|
16
|
+
|
|
17
|
+
Reads still return ISO strings, not `Date` instances. If you want a
|
|
18
|
+
`Date` back, hydrate at the boundary (`new Date(entity.expiresAt)`).
|
|
19
|
+
|
|
20
|
+
Issue: [#331](https://github.com/finlaysonstudio/jaypie/issues/331)
|