ai-capability-framework 1.1.0 → 1.1.1

package/CHANGELOG.md

@@ -4,6 +4,18 @@ All notable public changes to AI Capability Framework are documented here.
 
 ## Unreleased
 
+## 1.1.1 - 2026-10-26
+
+- Updated locked `fast-uri` to 3.1.9 and Zod to 4.6.7. The optional Zod peer now
+  requires 4.6.6 or newer, addressing URI normalization advisories and oversized
+  collection validation resource consumption. Lexical/native users do not need Zod.
+- Added weekly Dependabot npm update PRs for both packages, with manual review and CI
+  required. No automatic merge or publication is configured.
+- Added bounded dependency regressions and installed-consumer security checks. See
+  [consumer update instructions](SECURITY.md#dependency-security-updates): existing
+  application lockfiles require their own dependency refresh. Host input limits remain
+  necessary. Framework APIs, retrieval and authorization behavior are unchanged.
+
 ## 1.1.0 - 2026-10-17
 
 - Fixed the installed CLI's POSIX symlink entrypoint so `npx aicf` runs commands instead

package/SECURITY.md

@@ -41,6 +41,46 @@ redacted or removed to protect users.
 - MCP server integrations and caller-provided identity context.
 - Host policy, auth, storage, and provider adapter hooks.
 
+## Dependency Security Updates
+
+Version 1.1.1 raises the optional Zod minimum to 4.6.6 and updates the repository's
+locked Zod to 4.6.7 and `fast-uri` to 3.1.9. Zod's collection-validation issue can
+consume excessive memory; the `fast-uri` advisories concern URI normalization and
+reference handling. See the
+[Zod advisory](https://github.com/advisories/GHSA-mrhx-c7xc-m3w5) and
+[URI advisory](https://github.com/advisories/GHSA-w74x-v6f9-j3xg).
+
+Publishing a framework patch does not rewrite an application's existing lockfile. Update
+and verify your application dependencies:
+
+```sh
+npm install ai-capability-framework@1.1.1
+npm update fast-uri
+npm ls fast-uri zod
+npm audit --omit=dev
+```
+
+If your application already uses Zod, also update it:
+
+```sh
+npm install zod@^4.6.6
+```
+
+Then repeat the dependency listing, audit and application tests. `npm update fast-uri`
+selects a compatible patched release within the installed dependency ranges; for the
+framework's current Ajv resolution this is 3.1.9. Do not use a forced major upgrade or
+assume a clean new installation repairs a different application's pinned dependency
+tree. Lexical/native discovery needs neither Zod nor an optional provider SDK.
+
+Maintain host request-size and collection limits. A patched validator does not turn an
+unbounded application schema into a bounded one.
+
+Dependabot monitors npm dependencies in both packages and proposes weekly version
+updates on Monday at 05:00 Europe/London. Security alerts and security-update PRs
+operate separately from that weekly schedule. Dependency PRs require review and passing
+CI; they do not merge or publish automatically. The existing weekly audit remains
+enabled.
+
 ## Public Safety
 
 Security fixes should preserve the repository boundary:

package/docs/release.md

@@ -15,9 +15,9 @@ live trials.
 Use a reviewed pull request, passing hosted Linux Node 20/22/24 checks, merge, and an
 exact-commit manual release dry-run before pushing the matching version tag. Local
 checks do not replace hosted checks. Prereleases publish both packages to `next`,
-preserving `latest` for prereleases. Stable 1.1.0 publishes to `latest` while preserving
-the existing `next` tag and prerelease versions. Verify normal installation as well as
-exact-version registry installs.
+preserving `latest` for prereleases. Stable releases publish to `latest` while
+preserving the existing `next` tag and prerelease versions. Verify normal installation
+as well as exact-version registry installs.
 
 The publication and dry-run workflows run `npm run check` plus certification with
 `VITEST_MAX_WORKERS=2`. Publication is serialized; registry failures fail closed unless
@@ -25,6 +25,13 @@ npm explicitly reports E404 for an absent version. Local npm login is not the OI
 publishing mechanism. Verify package ownership and the trusted publisher for both
 packages before tagging; never substitute a stored npm token.
 
+For dependency security patches, include the
+[consumer lockfile update instructions](../SECURITY.md#dependency-security-updates) and
+verify both an SDK-free consumer and the minimum supported optional peer version.
+Repository lockfile changes alone do not update existing applications. Retain the frozen
+discovery qualification evidence; dependency maintenance does not establish new
+model-quality results.
+
 ## Preflight
 
 - Confirm the release branch contains only public framework material.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-capability-framework",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "private": false,
   "description": "Provider-agnostic AI capability contracts, runtime controls, evals, and model/provider adapters.",
   "license": "MIT",
@@ -336,7 +336,7 @@
     "ai": ">=6.0.0",
     "langchain": ">=1.4.0 <2",
     "openai": ">=4.0.0",
-    "zod": ">=4.4.3"
+    "zod": ">=4.6.6"
   },
   "peerDependenciesMeta": {
     "@aws-sdk/client-cloudwatch": {
@@ -410,6 +410,6 @@
     "typedoc": "^0.28.19",
     "typescript": "^6.0.3",
     "vitest": "^4.1.8",
-    "zod": "^4.4.3"
+    "zod": "^4.6.6"
   }
 }