@jaypie/mcp 0.8.32 → 0.8.33

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.32#bca51f2d"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.33#a3785407"
     ;
 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.32",
+  "version": "0.8.33",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/constructs/1.2.45.md

@@ -0,0 +1,25 @@
+---
+version: 1.2.45
+date: 2026-04-15
+summary: JaypieDistribution WAF resources support per-distribution namespacing via required `waf.name`
+---
+
+## Changes
+
+- `JaypieWafConfig.name` is now required whenever a WAF config object is passed to `JaypieDistribution`
+- When set, `name` is injected into both the WebACL name and the WAF log bucket name so multiple `JaypieDistribution` instances can coexist in one account/env
+- `waf: true` and absent `waf` continue to produce the legacy, non-namespaced names — existing deployments redeploy without change
+
+## Why
+
+Two `JaypieDistribution` instances in the same env collided on `aws-waf-logs-<env>-<key>-waf-<nonce>` (global S3 name) and the `WebACL` name. The only workarounds were disabling WAF or the log bucket. Requiring `waf.name` on object configs forces a unique suffix exactly where collisions are possible, while leaving the common `waf: true` path untouched. Resolves #297.
+
+## Migration
+
+Anywhere a WAF config object is passed — e.g. `waf: { rateLimitPerIp: 500 }` — add a `name`:
+
+```typescript
+waf: { name: "api", rateLimitPerIp: 500 }
+```
+
+Stacks using `waf: true` (or omitting `waf`) need no changes.

package/release-notes/mcp/0.8.33.md

@@ -0,0 +1,10 @@
+---
+version: 0.8.33
+date: 2026-04-15
+summary: Update cdk skill examples for `@jaypie/constructs` WAF `name` requirement
+---
+
+## Changes
+
+- `cdk` skill: WAF config examples now pass `waf.name` (required on any object-form config as of `@jaypie/constructs@1.2.45`)
+- Added a collision-avoidance example showing two `JaypieDistribution` instances with distinct `waf.name` values

package/skills/cdk.md

@@ -318,34 +318,40 @@ new JaypieDistribution(this, "Dist", { handler });
 // Disable WAF entirely
 new JaypieDistribution(this, "Dist", { handler, waf: false });
 
-// Customize rate limit
+// Customize rate limit (name required on any waf config object)
 new JaypieDistribution(this, "Dist", {
   handler,
-  waf: { rateLimitPerIp: 500 },
+  waf: { name: "api", rateLimitPerIp: 500 },
 });
 
+// Multiple distributions in one env — set a unique waf.name on each to
+// avoid WebACL/S3 bucket name collisions between stacks.
+new JaypieDistribution(this, "Api", { handler: api, waf: { name: "api" } });
+new JaypieDistribution(this, "Mcp", { handler: mcp, waf: { name: "mcp" } });
+
 // Use existing WebACL
 new JaypieDistribution(this, "Dist", {
   handler,
-  waf: { webAclArn: "arn:aws:wafv2:..." },
+  waf: { name: "api", webAclArn: "arn:aws:wafv2:..." },
 });
 
 // Disable WAF logging only
 new JaypieDistribution(this, "Dist", {
   handler,
-  waf: { logBucket: false },
+  waf: { name: "api", logBucket: false },
 });
 
 // Bring your own WAF logging bucket
 new JaypieDistribution(this, "Dist", {
   handler,
-  waf: { logBucket: myWafBucket },
+  waf: { name: "api", logBucket: myWafBucket },
 });
 
 // Override specific managed rule actions (e.g., allow large request bodies)
 new JaypieDistribution(this, "Dist", {
   handler,
   waf: {
+    name: "api",
     managedRuleOverrides: {
       AWSManagedRulesCommonRuleSet: [
         { name: "SizeRestrictions_BODY", actionToUse: { count: {} } },