From 0d5727a05a965982adc0af7f80de3b3fc55a3f04 Mon Sep 17 00:00:00 2001 From: Masterplanner25 Date: Mon, 16 Nov 2026 21:54:12 -0700 Subject: [PATCH] release: 2.36.1 Security patch: dnspython 2.9.2 for GHSA-vvf4-9x63-8xvv (FR-69, #975) plus the 2026-11-16 dependency batch. No schema step, no behaviour change. Co-Authored-By: Claude Opus 5.5 --- AINDY/_version.py | 2 +- CHANGELOG.md | 31 +++++++++++ CLAUDE.md | 2 +- Dockerfile | 2 +- changelog.d/975-deps-batch-2026-11-16.md | 20 ------- docs/upgrades/APP_HANDOFF_v2.36.1.md | 71 ++++++++++++++++++++++++ docs/upgrades/README.md | 3 +- 7 files changed, 107 insertions(+), 24 deletions(-) delete mode 100644 changelog.d/975-deps-batch-2026-11-16.md create mode 100644 docs/upgrades/APP_HANDOFF_v2.36.1.md diff --git a/AINDY/_version.py b/AINDY/_version.py index 07d3c71f..a1e72aab 100644 --- a/AINDY/_version.py +++ b/AINDY/_version.py @@ -1 +1 @@ -__version__ = "2.36.0" +__version__ = "2.36.1" diff --git a/CHANGELOG.md b/CHANGELOG.md index 7ed985a3..4ffb5a8c 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,37 @@ _Nothing yet._ +## 2.36.1 — 2026-11-16 + +**Operator notes — read before upgrading.** Handoff: `docs/upgrades/APP_HANDOFF_v2.36.1.md`. +**Security patch: rebuild the image.** No schema step (Alembic `0022`, contract `2026-11-09`, both unchanged). +No runtime behaviour, route, scope or default changed. No ui-kit or aindy-sdk release. + +- **★ `dnspython` 2.9.2** (CVE-2026-128089 / GHSA-vvf4-9x63-8xvv, high). Exposure nil in practice, but every pip-audit flags a 2.36.0 image. Drop any audit ignore you added for it. +- **`python-dateutil` 4.0.0**: `isoparse` now refuses numeric fields that are not exactly the expected digits (`2014- 4-21`, `20200728121240`). The runtime does not import it; check your own `isoparse` callers. + +### Fixed — `dnspython` 2.9.0 → 2.9.2 for CVE-2026-128089 / GHSA-vvf4-9x63-8xvv (FR-69, #975) + +- `dns.rdata.from_text()` did not bound a WKS record's service number, so crafted zone-file text + allocated memory without limit (high, availability only). The exact pin held every downstream + install on 2.9.0: the app could not constrain past it and carried an audit ignore (its FR-69). +- The runtime's exposure is nil in practice: nothing in `AINDY/` imports `dns`, and pymongo uses + only dnspython's resolver (wire format, for `mongodb+srv`), never zone-file text. Still an exact + pin: DEC-102's range exception is for the CA bundle only. + +### Changed — dependency batch of 2026-11-16 (#975) + +- Runtime pins: `python-dateutil` 3.0.0 → 4.0.0 (requires Python >= 3.11, which this package + already does; drops its `six` dependency; `isoparse` is stricter about numeric fields; nothing in + `AINDY/` imports it), `idna` 3.19 → 3.20 (Unicode 18), `regex` 2026.9.29 → 2026.11.9, `tzlocal` + 5.4.4 → 5.4.5. +- Native crate: `cc` 1.11.1 → 1.11.2, `uuid` 1.29.1 → 1.29.2. Platform UI (dev): `vite` 8.3.6 → + 8.3.8, `@vitejs/plugin-react` 6.2.1 → 6.3.0, `postcss` 8.5.32 → 8.5.33. +- `SQLAlchemy` stays on 2.0.x: 2.1 resolves a bare `postgresql://` URL to psycopg 3 rather than the + `psycopg2` this package ships, so engine creation fails on PostgreSQL. Deferred under + DEP-UPGRADE-DEFERRED-1. + + ## 2.36.0 — 2026-11-11 **Operator notes — read before upgrading.** Handoff: `docs/upgrades/APP_HANDOFF_v2.36.0.md`. diff --git a/CLAUDE.md b/CLAUDE.md index 1c81c6cd..296f63fe 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -362,7 +362,7 @@ Adding a `SystemEventTypes` value: regenerate `tests/baselines/system_event_cont | Runtime contracts (idempotency, sandbox, connector, SDK, UI, invariants, durable-state ownership) | `docs/runtime/*_CONTRACT.md`, `EXECUTION_INVARIANTS.md`, `SECURITY_MATRIX.md`, `SYSCALL_REFERENCE.md`, `NODUS_DEVELOPER_GUIDE.md` | | Design records index (every scope/design doc + status) | `docs/design/README.md` | | Comparative research index (8 systems; what is settled) | `docs/governance/COMPARATIVE_RESEARCH_INDEX.md` | -| Release checklist; upgrades index; latest app handoff | `docs/governance/RELEASE_CHECKLIST.md`; `docs/upgrades/README.md`; `docs/upgrades/APP_HANDOFF_v2.36.0.md` | +| Release checklist; upgrades index; latest app handoff | `docs/governance/RELEASE_CHECKLIST.md`; `docs/upgrades/README.md`; `docs/upgrades/APP_HANDOFF_v2.36.1.md` | | Outbound handoffs to Nodus | `docs/handoffs/README.md` | | Route ownership; deployment targets | `docs/runtime/ROUTE_OWNERSHIP_INVENTORY.md`; `docs/operations/DEPLOYMENT_TARGETS.md` | | Sibling repos | ui-kit `C:\dev\aindy-ui-kit\src\`; apps monolith `C:\dev\aindy-apps-monolith\CLAUDE.md` | diff --git a/Dockerfile b/Dockerfile index deee0b0a..19eaae33 100644 --- a/Dockerfile +++ b/Dockerfile @@ -33,7 +33,7 @@ RUN apt-get update && apt-get install -y --no-install-recommends \ # SPA dist via package-data. `packaging` is a declared dependency but pip # treats it as a bootstrap package and skips it in --prefix installs; force # it in so it propagates to the runtime stage. -RUN pip install --prefix=/install "aindy-runtime==2.36.0" \ +RUN pip install --prefix=/install "aindy-runtime==2.36.1" \ && pip install --prefix=/install --ignore-installed "packaging>=24.0" diff --git a/changelog.d/975-deps-batch-2026-11-16.md b/changelog.d/975-deps-batch-2026-11-16.md deleted file mode 100644 index c8109d68..00000000 --- a/changelog.d/975-deps-batch-2026-11-16.md +++ /dev/null @@ -1,20 +0,0 @@ -### Fixed — `dnspython` 2.9.0 → 2.9.2 for CVE-2026-128089 / GHSA-vvf4-9x63-8xvv (FR-69, #975) - -- `dns.rdata.from_text()` did not bound a WKS record's service number, so crafted zone-file text - allocated memory without limit (high, availability only). The exact pin held every downstream - install on 2.9.0: the app could not constrain past it and carried an audit ignore (its FR-69). -- The runtime's exposure is nil in practice: nothing in `AINDY/` imports `dns`, and pymongo uses - only dnspython's resolver (wire format, for `mongodb+srv`), never zone-file text. Still an exact - pin: DEC-102's range exception is for the CA bundle only. - -### Changed — dependency batch of 2026-11-16 (#975) - -- Runtime pins: `python-dateutil` 3.0.0 → 4.0.0 (requires Python >= 3.11, which this package - already does; drops its `six` dependency; `isoparse` is stricter about numeric fields; nothing in - `AINDY/` imports it), `idna` 3.19 → 3.20 (Unicode 18), `regex` 2026.9.29 → 2026.11.9, `tzlocal` - 5.4.4 → 5.4.5. -- Native crate: `cc` 1.11.1 → 1.11.2, `uuid` 1.29.1 → 1.29.2. Platform UI (dev): `vite` 8.3.6 → - 8.3.8, `@vitejs/plugin-react` 6.2.1 → 6.3.0, `postcss` 8.5.32 → 8.5.33. -- `SQLAlchemy` stays on 2.0.x: 2.1 resolves a bare `postgresql://` URL to psycopg 3 rather than the - `psycopg2` this package ships, so engine creation fails on PostgreSQL. Deferred under - DEP-UPGRADE-DEFERRED-1. diff --git a/docs/upgrades/APP_HANDOFF_v2.36.1.md b/docs/upgrades/APP_HANDOFF_v2.36.1.md new file mode 100644 index 00000000..59f277f8 --- /dev/null +++ b/docs/upgrades/APP_HANDOFF_v2.36.1.md @@ -0,0 +1,71 @@ +--- +title: "App Handoff — Runtime v2.36.1" +api_version: "1.0" +last_verified: "2026-11-16" +status: current +owner: "platform-team" +--- + +# App handoff: runtime v2.36.1 + +**A security patch that answers FR-69.** `dnspython` moves 2.9.0 → 2.9.2. The rest is the 2026-11-16 dependency +batch (#975). No runtime behaviour, route, scope or default changed. **No schema step**: Alembic stays at `0022` and +the schema contract at `2026-11-09`. No ui-kit or aindy-sdk release. + +Bump the `constraints.txt` pin to `==2.36.1` (your contract test moves the floor with it), **rebuild the image** +(`mcp` shares it, so recreate both), and **remove your audit ignore for GHSA-vvf4-9x63-8xvv**. + +> ## ★ After the rebuild: confirm what you are running +> +> ```bash +> docker exec python -c "import AINDY, AINDY._version as v, importlib.metadata as m; print(v.__version__, m.version('dnspython'), m.version('python-dateutil'), list(AINDY.__path__))" +> # expect: 2.36.1 2.9.2 4.0.0 ['/usr/local/lib/python3.11/site-packages/AINDY'] +> ``` + +--- + +## 1. ★ FR-69: `dnspython` 2.9.2 (#975) + +| Advisory | Package | Fixed in | Severity | Runtime exposure | +|---|---|---|---|---| +| CVE-2026-128089 / GHSA-vvf4-9x63-8xvv | `dnspython` 2.9.0 | 2.9.2 | high, availability | **Nil in practice.** `from_text()` did not bound a WKS record's service number, so crafted zone-file text allocates without limit. Nothing in `AINDY/` imports `dns`; pymongo uses only the resolver (wire format, for `mongodb+srv`). Your assessment in FR-69 matches ours. | + +**Still an exact pin, not the range you asked for.** The owner chose `==2.9.2`: DEC-102's range exception is for +certifi alone, because a CA bundle's newest release is the safest one by construction. dnspython has an API, so that +argument does not carry over. The cost you named stays: a future dnspython advisory needs another runtime patch. We +will cut one the same way. + +**FR-69 closes** when you are on 2.36.1 and your audit runs clean with the ignore removed. Report both in your +upgrade note. + +## 2. `python-dateutil` 4.0.0: read if your code calls `isoparse` + +The runtime does not import `dateutil`; it arrives through `pendulum`. 4.0 requires Python ≥ 3.11 (the image is +3.11) and drops its `six` dependency. Its one behavioural change: **`parser.isoparse` (and `parse_isodate`, +`parse_isotime`, `parse_tzstr`) now require each numeric field to be exactly the expected number of ASCII digits.** +Strings that used to parse, such as `20200728121240`, `2014- 4-21`, `2_14-04-21`, or an offset like `+-1:00`, now +raise `ValueError`. `tzical` applies the same check to `TZOFFSETFROM`/`TZOFFSETTO`. Also fixed: `relativedelta(yearday=366)` +now lands on Dec 31 in leap years, and a cached `rrule` iterated twice no longer hangs. + +If app code calls `isoparse` on input it does not control, check what it does with a `ValueError`. + +## 3. The rest of the batch (#975) + +| Package | From → to | Where | +|---|---|---| +| `idna` | 3.19 → 3.20 | runtime (Unicode 18; domain-length check in the incremental codec) | +| `regex` / `tzlocal` | 2026.9.29 → 2026.11.9 / 5.4.4 → 5.4.5 | runtime | +| `vite` / `@vitejs/plugin-react` / `postcss` | 8.3.6 → 8.3.8 / 6.2.1 → 6.3.0 / 8.5.32 → 8.5.33 | platform SPA, dev (shipped prebuilt in the wheel) | +| `cc` / `uuid` | 1.11.1 → 1.11.2 / 1.29.1 → 1.29.2 | native crate, build-time only | + +**Not taken: SQLAlchemy 2.1.** It resolves a bare `postgresql://` URL to psycopg 3, and the runtime ships `psycopg2`, +so engine creation fails on PostgreSQL. The runtime stays on 2.0.52; the migration is deferred under +`DEP-UPGRADE-DEFERRED-1`. If you pin SQLAlchemy yourself, stay on 2.0.x. + +## 4. Your register + +- **FR-67 and FR-68: closed** on your 2.36.0 report (runtime #974). Thanks for the counts. The 1,904 ownerless nodes + the backfill left alone are by design (DEC-119): a node with no owner has no tenant to put in its path, so it never gets a stored one. +- **FR-70** (a narrow credential for app routes): received and verified in source. It needs a decision between your + two options, so it is not in this patch. It gets its own release. +- Still open from earlier handoffs, no new ask: the trace question in your 2.34.0 report (§5 there). diff --git a/docs/upgrades/README.md b/docs/upgrades/README.md index 6c3e27e6..51911899 100644 --- a/docs/upgrades/README.md +++ b/docs/upgrades/README.md @@ -1,6 +1,6 @@ --- title: "Upgrading aindy-runtime" -last_verified: "2026-11-11" +last_verified: "2026-11-16" api_version: "1.0" status: current owner: "platform-team" @@ -87,6 +87,7 @@ loop, not a warning (`FR-14`, 2.1.0). Read the exit code — `0` done, `3` re-ru | **2.34.0** | 2026-11-08 | [`APP_HANDOFF_v2.34.0.md`](./APP_HANDOFF_v2.34.0.md) | none | `0021` | `2026-11-08` | no | **★ Run `events backfill-call-users` once.** The app's FR-61..64: outbound-call events name their user (DEC-123), `backfill-paths --yes` works, provider-key errors pass through the chat helpers, a retried-out node keeps its error, and a failing handler rolls back only its own work (DEC-124). | | **2.35.0** | 2026-11-10 | [`APP_HANDOFF_v2.35.0.md`](./APP_HANDOFF_v2.35.0.md) | **yes** — `mcp_oauth_clients`, `mcp_oauth_grants` | `0022` | `2026-11-09` | no | **`bootstrap-schema --reconcile` required.** **★ An MCP server refuses to start exposing a syscall without `read_only=True` unless `ALLOW_WRITES`** (DEC-128) — declare your reads in the same change as the pin. FR-66: streamable HTTP + OAuth for `/mcp`, off by default. FastAPI 0.162. Pairs with `aindy-sdk` 1.2.1 (FR-65). | | **2.36.0** | 2026-11-11 | [`APP_HANDOFF_v2.36.0.md`](./APP_HANDOFF_v2.36.0.md) | none | `0022` | `2026-11-09` | no | **★ Run `memory backfill-paths` once** (dry run, then `--yes`): stored paths end with their node's id (FR-67, DEC-131); ids never change, old addresses stop resolving. `memory.write` refuses a `path` that names its last segment. **FR-68:** set `FORWARDED_ALLOW_IPS` on `mcp-server` behind a proxy (DEC-132). nodus-lang 5.16.0 (error columns change). | +| **2.36.1** | 2026-11-16 | [`APP_HANDOFF_v2.36.1.md`](./APP_HANDOFF_v2.36.1.md) | none | `0022` | `2026-11-09` | no | **Security patch — rebuild the image.** ★ `dnspython` 2.9.2 (CVE-2026-128089, exposure nil; closes FR-69 — drop your audit ignore). `python-dateutil` 4.0.0 makes `isoparse` stricter (runtime unaffected; check your own uses). SQLAlchemy stays 2.0.x. No behaviour change. Asks: pin bump, rebuild, remove the ignore. | | **2.27.0** | 2026-10-09 | [`APP_HANDOFF_v2.27.0.md`](./APP_HANDOFF_v2.27.0.md) | none | `0020` | `2026-09-20` | no | Pin bump + rebuild, no schema step (the `Upgrade Path Guard`'s meaning rests on its negative control). **★ python-jose → `PyJWT[crypto]`** (FR-51, CVE-2026-85394, no fix upstream): `ecdsa`, `rsa`, `pyasn1` leave the install; tokens byte-identical, sessions survive. **`pymongo` 4.18.2** (CVE-2026-96747/8/9). **FR-52:** the per-request ~3 s DEBT-COMPAT-1 metadata scan now runs once per plugin set. starlette 1.7.0, pyphen 0.18.1, regex, mako, charset-normalizer. Asks: drop the four FR-51 audit ignores; re-measure FR-52 latency. | | **2.26.0** | 2026-10-04 | [`APP_HANDOFF_v2.26.0.md`](./APP_HANDOFF_v2.26.0.md) | none | `0020` | `2026-09-20` | no | Pin bump + rebuild, no schema step (the `Upgrade Path Guard`'s meaning rests on its negative control). **★ Three defaults ON:** `AINDY_PLAN_STEP_REFERENCES` (FR-46, DEC-084), `AINDY_RUN_SCOPED_QUOTA` (a run's syscalls count against one `AINDY_QUOTA_MAX_SYSCALLS`, default 100; wall time not summed; DEC-095/096), `AINDY_FLOW_FAN_OUT` (DEC-097; the runner no longer holds a transaction across a superstep). **EFFECT-OUTCOME-UNKNOWN-1:** `unknown`/`partial` held on replay, `AT_MOST_ONCE`, `outbound_request` no longer retries a possibly-processed POST/PATCH, admin `GET /platform/effects/unknown` + `POST /platform/effects/{action_id}/resolve`. **FS-SCOPE-1:** declared filesystem scope enforced on both seams (Python, not kernel). On-demand latency floor. Asks: grep `RESOURCE_LIMIT_EXCEEDED` after first runs; the recall-failure readout (>= 10-09) before rebuilding. | | **2.24.0** | 2026-09-26 | [`APP_HANDOFF_v2.24.0.md`](./APP_HANDOFF_v2.24.0.md) | none | `0020` | `2026-09-20` | no | Pin bump + **`@aindy/ui-kit` 2.1.1** + rebuild, no migration — but **FR-43**: `bootstrap-schema` now sees a column widening (a stack still at `system_events.source` 32 exits **3**; corrects the 2.22.0 handoff's exit-3 promise). **FR-44** resume arms the wait (`run_status` may be `"waiting"`), **FR-45** runtime adapters stamp, **FR-46** step references (flag off), **IDEM-14** tool key per step (`execute_tool(step_index=)` — stubs), **FR-47** ui-kit `timeoutMs` (a caller's abort is no longer 408). nodus-lang 5.15.0. Asks: FR-46 evidence run, FR-44 two-process re-run. |