@jaypie/mcp 0.8.160 → 0.8.161

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.
package/dist/assets.js CHANGED
@@ -55,11 +55,11 @@ function getMcpAssetPaths() {
55
55
  */
56
56
  function getMcpBuildInfo() {
57
57
  return {
58
- commit: "b6d2f24e"
58
+ commit: "89205145"
59
59
  ,
60
- version: "0.8.160"
60
+ version: "0.8.161"
61
61
  ,
62
- versionString: "@jaypie/mcp@0.8.160#b6d2f24e"
62
+ versionString: "@jaypie/mcp@0.8.161#89205145"
63
63
  ,
64
64
  };
65
65
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jaypie/mcp",
3
- "version": "0.8.160",
3
+ "version": "0.8.161",
4
4
  "description": "Jaypie MCP",
5
5
  "repository": {
6
6
  "type": "git",
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  version: 0.3.9
3
3
  date: 2026-08-02
4
- summary: fabricTool({ external: true }) emits a call-less external tool; structural LlmTool becomes the callable/external union
4
+ summary: "fabricTool({ external: true }) emits a call-less external tool; structural LlmTool becomes the callable/external union"
5
5
  ---
6
6
 
7
7
  ## Changes
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  version: 1.2.6
3
3
  date: 2026-05-10
4
- summary: Add migrationHandler that defaults throw: true so failed migrations fail the deploy (issue #339)
4
+ summary: "Add migrationHandler that defaults throw: true so failed migrations fail the deploy (issue #339)"
5
5
  ---
6
6
 
7
7
  ## Changes
@@ -0,0 +1,25 @@
1
+ ---
2
+ version: 0.8.161
3
+ date: 2026-09-16
4
+ summary: "Quote two release note summaries containing `: ` and add a frontmatter parse check over release-notes/ and skills/"
5
+ ---
6
+
7
+ ## Changes
8
+
9
+ ### Bug Fixes
10
+
11
+ - Quote the `summary` frontmatter value in `fabric/0.3.9.md` and
12
+ `lambda/1.2.6.md`. Both contained an unquoted `: `, which YAML read as a
13
+ nested mapping key, so the block failed to parse and `release_notes` returned
14
+ the notes without `date` or `summary` (issue #566).
15
+
16
+ ### New Features
17
+
18
+ - Add `documentFrontmatter.spec.ts`: every markdown file under `release-notes/`
19
+ and `skills/` must parse, and every release note must carry `date`,
20
+ `summary`, and `version`. A malformed block now fails the build.
21
+
22
+ ### Documentation
23
+
24
+ - `skills/releasenotes.md` and `packages/mcp/CLAUDE.md` state when a `summary`
25
+ requires double quotes.
@@ -66,7 +66,10 @@ Add release notes when:
66
66
 
67
67
  ## Writing Guidelines
68
68
 
69
- 1. **Summary** - One line, present tense, describes the release
69
+ 1. **Summary** - One line, present tense, describes the release. Wrap the
70
+ value in double quotes whenever it contains `:`, `#`, `{`, `[`, or a
71
+ leading `*`, `&`, or `!`; an unquoted `: ` makes YAML read the rest as a
72
+ nested mapping and the frontmatter fails to parse
70
73
  2. **Changes** - Group by type: New Features, Bug Fixes, Breaking Changes
71
74
  3. **Bullets** - Start with verb (Add, Fix, Update, Remove)
72
75
  4. **Links** - Reference issues/PRs when relevant