Build AI methods with your coding agent, then run them anywhere: as an MCP for chatbots, as a webapp for people, or via API for your software.
Merge branch 'main' into dev
Louis Choquel5d7ebad65343
diff --cc CHANGELOG.mdindex 9f45dc5bf,81df16f11..6f88195e3--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -1,14 -1,21 +1,25 @@@# Changelog- ## [Unreleased]+ ## [v0.43.1] - 2026-08-12++ ### Changed++ - **`PipeRunParams.batch_max_concurrency` is now required (Breaking)**: The field no longer defaults to `None`, which previously made an omitted value indistinguishable from an explicitly authored unbounded concurrency (`max_concurrency = "unbounded"`). Omitting it now raises a `ValidationError` early—on both direct construction and payload decoding—to prevent accidental unbounded fan-outs.+ - **Migration:** Construct `PipeRunParams` via `PipeRunParamsFactory.make_run_params()`, the single writer for run-scoped invariants (`run_mode`, `pipe_stack_limit`, `batch_max_concurrency`). Integration test fixtures now route through the factory via a new `make_mode_guarded_run_params` helper.+ - **Docs:** Added a warning to `docs/under-the-hood/pipe-routing-and-execution.md` on using the factory method.+### Changed++- **`PipeRunParams.batch_max_concurrency` is required (Breaking)**: The fan-out bound has no default any more, joining `run_mode` and `pipe_stack_limit` as a field whose omission fails loud. `None` is not only what a default would give — it is also what an authored `max_concurrency = "unbounded"` resolves to, so a default made "never written" indistinguishable from "authored unbounded", and pointed the omission at the dangerous direction: launch every branch at once. Breaking for code constructing `PipeRunParams` directly or decoding a payload that predates the field; build through `PipeRunParamsFactory.make_run_params`, the single writer of all three fields.+### Fixed- - **A `{concept, content}` envelope carrying an empty list is now a value, not an error**: a plural slot is never _absent_ — when nothing is found it is the empty list — and the top-down shaper has always honoured that for a bare `[]` (D2). The bottom-up factory did not: it infers a list's item type from the first item, so an empty list raised _"Cannot create Stuff from empty list in content"_. The two spellings of one input therefore disagreed — a caller with no pictures could send `[]` and run, or send `{"concept": "native.Image", "content": []}` and fail — which made a plural input with nothing in it unrunnable for every caller that wraps its inputs. The envelope names the concept, so there was never anything to infer; it now builds an empty `ListContent`. Case 1.5 (a bare empty `ListContent`, no concept anywhere) still raises, and must: nothing there says what the items would have been.+ - **Empty lists in concept envelopes are now parsed as values, not errors**: The bottom-up factory previously raised _"Cannot create Stuff from empty list in content"_ when given an empty list inside a concept envelope (e.g., `{"concept": "native.Image", "content": []}`). Since the envelope names the concept, item-type inference is unnecessary, so it now correctly yields an empty `ListContent`. This aligns the bottom-up factory with the top-down shaper; callers can pass `[]` or `{"concept": "...", "content": []}` to represent an empty plural slot. A bare empty list with no concept still raises an error, as its type cannot be inferred.+ - **Docs:** Added a note to `docs/building-methods/pipes/provide-inputs.md` clarifying that an empty list represents an empty plural slot, whereas omitting the key fails with a _"missing required inputs"_ error.++ ### Security++ - **`uv.lock` refreshed onto patched dependency versions**: A targeted lock refresh clears the open Dependabot alerts, with no `pyproject.toml` constraint changes — every declared range already permitted the patched version, so this was stale-lock drift rather than a constraint problem. Bumps `aiohttp`, `cryptography`, `datamodel-code-generator`, `pillow`, `pyasn1`, `pymdown-extensions` and `soupsieve`. The alerts left open are held by `torch`, reachable only through the optional `docling` extra, whose upgrade would drag `torchvision`, `triton` and the NVIDIA CUDA stack along with it.## [v0.43.0] - 2026-08-12