@jaypie/mcp 0.8.33 → 0.8.35
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.35#6b1947e4"
|
|
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,18 @@
|
|
|
1
|
+
---
|
|
2
|
+
version: 1.2.46
|
|
3
|
+
date: 2026-04-16
|
|
4
|
+
summary: JaypieEnvSecret throws ConfigurationError when envKey env var is missing or empty
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Changes
|
|
8
|
+
|
|
9
|
+
- `JaypieEnvSecret` now throws `ConfigurationError` at synth when `envKey` is set but `process.env[envKey]` is missing or empty and neither `value` nor `generateSecretString` was provided
|
|
10
|
+
- Consumers (ephemeral envs that import from a provider) continue to resolve the secret name via `Fn.importValue` and are not affected
|
|
11
|
+
|
|
12
|
+
## Why
|
|
13
|
+
|
|
14
|
+
Previously, a missing or empty `envKey` env var silently fell through to `secretsmanager.Secret` with both `secretStringValue` and `generateSecretString` undefined, which causes CDK to auto-generate a random JSON password. Deployments succeeded with the wrong value and consumers got 401s that were hard to attribute. Failing loudly at synth surfaces the configuration gap before it reaches Secrets Manager. Resolves #287.
|
|
15
|
+
|
|
16
|
+
## Migration
|
|
17
|
+
|
|
18
|
+
If you relied on CDK's auto-generated fallback, pass `generateSecretString: {}` (or a valid options object) explicitly, or provide a `value`.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
---
|
|
2
|
+
version: 1.2.25
|
|
3
|
+
date: 2026-04-15
|
|
4
|
+
summary: Fix Gemini structured output shape drift by switching to OpenAPI 3.0 responseSchema
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Changes
|
|
8
|
+
|
|
9
|
+
- Default Gemini structured output from `responseJsonSchema` (preview-tier) to `responseSchema` (OpenAPI 3.0 stable)
|
|
10
|
+
- Add `jsonSchemaToOpenApi3` utility that strips `$schema`, `additionalProperties`, `$defs`, `$ref`, `const` from JSON Schema
|
|
11
|
+
- Apply same OpenAPI 3.0 conversion in `formatOutputSchema` for the `structured_output` tool path
|
|
12
|
+
- Old behavior available via `providerOptions: { useJsonSchema: true }`
|
|
13
|
+
- Fixes ~30% shape drift where Gemini echoed the `items` keyword as a literal property in array responses
|