@jaypie/mcp 0.8.40 → 0.8.42

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.40#d3b7b298"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.42#4dd42146"
     ;
 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.40",
+  "version": "0.8.42",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/constructs/1.2.50.md

@@ -0,0 +1,21 @@
+---
+version: 1.2.50
+date: 2026-04-18
+summary: JaypieEnvSecret shorthand now validates missing env vars instead of silently creating empty secrets
+---
+
+## Changes
+
+- `JaypieEnvSecret` detects shorthand by convention: a SCREAMING_SNAKE_CASE string (e.g., `MONGODB_URI`, `ANTHROPIC_API_KEY`) as the second constructor argument is treated as an `envKey`, even when the env var is not set at deploy time.
+- When shorthand is used without a backing env var, `value`, or `generateSecretString`, construction throws `ConfigurationError` instead of silently producing an empty secret.
+- Non-shorthand PascalCase ids (e.g., `TestSecret`, `ProjectSalt`) continue to behave as before.
+
+## Motivation
+
+The prior shorthand detection required `process.env[name]` to be a non-empty string. A missing env var fell through to the plain-id branch and produced a secret with no value, which surfaced only at runtime via `loadEnvSecrets`. The new convention-based detection keeps shorthand calls on the envKey validation path regardless of env state.
+
+## Migration
+
+- Consumers already setting env vars at deploy time see no change.
+- Stacks relying on the old silent behavior should pass `value` or `generateSecretString`, or set the expected env var.
+- Provider/consumer shorthand pairs now derive the same `EnvSecret_*` construct id on both sides, fixing a latent export-name mismatch when the env var was unset in the consumer environment.

package/release-notes/express/1.2.23.md

@@ -0,0 +1,10 @@
+---
+version: 1.2.23
+date: 2026-04-18
+summary: Split query from path and add content metadata to express session report
+---
+
+## Changes
+
+- `expressHandler` session report now separates `query` from `path`. Query parameters are sorted alphabetically so `/ping?name=World&salutation=Hello` and `/ping?salutation=Hello&name=World` produce the same report entry.
+- Adds `contentType` and `contentLength` to the `log.report` payload, populated from the request `content-type` and `content-length` headers.

package/release-notes/jaypie/1.2.41.md

@@ -0,0 +1,9 @@
+---
+version: 1.2.41
+date: 2026-04-18
+summary: Pull in @jaypie/express 1.2.23 with enhanced session report
+---
+
+## Changes
+
+- Bumps `@jaypie/express` to `^1.2.23` which splits `query` from `path` and adds `contentType` / `contentLength` to the session report.

package/release-notes/mcp/0.8.41.md

@@ -0,0 +1,10 @@
+---
+version: 0.8.41
+date: 2026-04-18
+summary: Add release notes for express 1.2.23 and jaypie 1.2.41
+---
+
+## Changes
+
+- Adds release notes for `@jaypie/express` 1.2.23 (split query from path, report contentType/contentLength).
+- Adds release notes for `jaypie` 1.2.41.

package/release-notes/mcp/0.8.42.md

@@ -0,0 +1,10 @@
+---
+version: 0.8.42
+date: 2026-04-18
+summary: Update secrets skill and add release notes for constructs 1.2.50
+---
+
+## Changes
+
+- Updates `skills/secrets.md` to document convention-based shorthand detection and the new missing-env `ConfigurationError`.
+- Adds release notes for `@jaypie/constructs` 1.2.50.

package/skills/secrets.md

@@ -34,9 +34,12 @@ new JaypieLambda(this, "Handler", {
 });
 ```
 
-When the construct ID matches an environment variable name, `JaypieEnvSecret` automatically:
-- Uses that env var's value as the secret content
-- Sets `envKey` to the ID for later reference
+When the construct ID is a SCREAMING_SNAKE_CASE string (or matches an environment variable name with a non-empty value), `JaypieEnvSecret` automatically:
+- Treats the ID as the `envKey`
+- Uses the env var's value as the secret content
+- Namespaces the CDK construct id as `EnvSecret_${envKey}`
+
+If the shorthand env var is missing at deploy time and no `value` or `generateSecretString` is provided, construction throws `ConfigurationError`. Supply a `value` or `generateSecretString` when the env var may be absent.
 
 ### CI/CD Setup