@jaypie/mcp 0.8.36 → 0.8.38

package/dist/suites/docs/index.js

@@ -9,7 +9,7 @@ import { gt } from 'semver';
 /**
  * Docs Suite - Documentation services (skill, version, release_notes)
  */
-const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.36#59e1a274"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.38#ff8c48d7"
     ;
 const __filename$1 = fileURLToPath(import.meta.url);
 const __dirname$1 = path.dirname(__filename$1);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jaypie/mcp",
-  "version": "0.8.36",
+  "version": "0.8.38",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/aws/1.2.8.md

@@ -0,0 +1,9 @@
+---
+version: 1.2.8
+date: 2026-04-17
+summary: Fix getTextractJob termination for non-success job states
+---
+
+## Changes
+
+- `getTextractJob` now actually exits the fetch loop on `IN_PROGRESS`, `FAILED`, and unknown job statuses. Previously the terminal cases set `doneFetching = true`, only to have it overwritten by the unconditional `doneFetching = !response.NextToken` assignment at the end of the loop body. Terminal cases now `continue` so the `while (!doneFetching)` check exits cleanly.

package/release-notes/constructs/1.2.47.md

@@ -0,0 +1,9 @@
+---
+version: 1.2.47
+date: 2026-04-17
+summary: Remove dead post-increment in JaypieDistribution WAF rule priority
+---
+
+## Changes
+
+- Removed a useless `priority++` on the last use of the `priority` counter when building WAF rules in `JaypieDistribution`. No behavior change.

package/release-notes/core/1.2.2.md

@@ -0,0 +1,9 @@
+---
+version: 1.2.2
+date: 2026-04-17
+summary: Remove dead initializer in deprecated validate()
+---
+
+## Changes
+
+- Dropped an unused `let valid = false` initializer in the deprecated `validate()` function. No behavior change.

package/release-notes/eslint/1.2.3.md

@@ -0,0 +1,17 @@
+---
+version: 1.2.3
+date: 2026-04-17
+summary: Support ESLint 10 in addition to ESLint 9
+---
+
+## Changes
+
+- Peer dependency widened to `eslint: "^9.0.0 || ^10.0.0"`
+- Bumped `@eslint/js` to `^10.0.0` (strict major peer)
+- Bumped supporting plugins: `typescript-eslint` 8.58, `@vitest/eslint-plugin` 1.6, `eslint-plugin-import-x` 4.16, `eslint-plugin-prettier` 5.5, `eslint-config-prettier` 10.1, `eslint-import-resolver-typescript` 4.4, `globals` 17
+
+## Notes
+
+ESLint 10's `@eslint/js` recommended config adds `no-useless-assignment`, `no-unassigned-vars`, and `preserve-caught-error`. Existing code that relies on the v9 rule set may surface new errors on upgrade.
+
+Node engines: ESLint 10 requires `^20.19.0 || ^22.13.0 || >=24`.

package/release-notes/jaypie/1.2.39.md

@@ -0,0 +1,12 @@
+---
+version: 1.2.39
+date: 2026-04-17
+summary: Bump @jaypie/aws, @jaypie/core, @jaypie/llm deps
+---
+
+## Changes
+
+- Dependency bumps:
+  - `@jaypie/aws` ^1.2.7 → ^1.2.8
+  - `@jaypie/core` ^1.2.1 → ^1.2.2
+  - `@jaypie/llm` ^1.2.27 → ^1.2.28 (peer)

package/release-notes/llm/1.2.27.md

@@ -0,0 +1,11 @@
+---
+version: 1.2.27
+date: 2026-04-17
+summary: Update ANTHROPIC.LARGE to claude-opus-4-7
+---
+
+## Changes
+
+- `PROVIDER.ANTHROPIC.MODEL.LARGE` bumped from `claude-opus-4-6` to `claude-opus-4-7` (the current flagship Anthropic model)
+- No behavior change for other providers; Gemini, OpenAI, and xAI model constants already reflect their latest URLs
+- Opus 4.7 is already covered by the existing `claude-opus-4-[789]` temperature denylist, so requests with temperature are stripped automatically

package/release-notes/llm/1.2.28.md

@@ -0,0 +1,12 @@
+---
+version: 1.2.28
+date: 2026-04-17
+summary: Internal cleanups surfaced by ESLint 10
+---
+
+## Changes
+
+- `GeminiAdapter` stream path: replaced a `let`+null-reset pattern with a block-scoped `const` for the in-flight function call. No behavior change.
+- `providers/gemini/utils.ts`: removed an always-`undefined` `let systemInstruction` declaration; the return shape still exposes `systemInstruction: undefined` for callers that destructure it.
+- `tools/weather`: preserves existing vanilla-`Error` throws with an inline eslint-disable — the package targets ES2020 and `Error`'s `cause` option requires ES2022.
+- Test fixtures (`test/document.ts`, `test/structured.ts`): dropped dead `success = false` initializers.

package/release-notes/mcp/0.8.38.md

@@ -0,0 +1,17 @@
+---
+version: 0.8.38
+date: 2026-04-17
+summary: Add release notes for the ESLint 10 upgrade batch
+---
+
+## Changes
+
+Added release notes for the packages bumped during the ESLint 10 upgrade branch:
+
+- `@jaypie/aws@1.2.8`
+- `@jaypie/constructs@1.2.47`
+- `@jaypie/core@1.2.2`
+- `@jaypie/eslint@1.2.3`
+- `@jaypie/llm@1.2.28`
+- `@jaypie/testkit@1.2.34`
+- `jaypie@1.2.39`

package/release-notes/testkit/1.2.34.md

@@ -0,0 +1,9 @@
+---
+version: 1.2.34
+date: 2026-04-17
+summary: Remove dead assignments in lambda/websocket mock handlers
+---
+
+## Changes
+
+- Cleaned up dead `props = temp` assignments in `lambdaStreamHandler` and `websocketHandler` swap branches — no behavior change, surfaced by ESLint 10's new `no-useless-assignment` rule.

package/skills/monorepo.md

@@ -9,7 +9,7 @@ Initialize a new monorepo using Jaypie conventions and utilities.
 
 ## Overview
 
-- ESLint 9+ flat config with @jaypie/eslint
+- ESLint 9 or 10 flat config with @jaypie/eslint
 - NPM with Workspaces ("monorepo")
 - TypeScript with ESM modules
 - Vite for building, Vitest for testing