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.
Release v0.50.0
thomashebrardf34967bf01e2
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 200a05b2d..847773bd7 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -1,6 +1,8 @@# Changelog-## Unreleased+## [v0.50.0] - 2026-08-20++### Changed- **Breaking: `JobMetadata` splits its run-constant half into a new `RunMetadata`.** `user_id`, `pipeline_run_id`, `storage_scope` and `request_id` are constant for a whole run; `pipe_code`, `pipe_run_id`, `otel_context` and `content_generation_job_id` change at every step. They sat side by side with nothing saying which was which, so a copy made for a nested pipe had to know, field by field, what to carry through. They are now `job_metadata.run_metadata.*`, and the copy carries one object.@@ -12,8 +14,6 @@Set at the run boundary and **not** at the ~17 `PipeOutput(...)` construction sites: only the top-level output crosses a transport boundary, and stamping every constructor to serve one of them is the same "remember to add it everywhere" fragility that caused the original bug. Optional throughout — dry runs, signature stubs and tests build outputs with no job in hand — and invisible on the wire, since `serialize_completed_output` names the fields it returns explicitly.-- **The `error_type` values a validation verdict can carry are now an enumerable, closed registry**: a `.mthds` bundle that fails validation reports each fault under an `error_type`, and until now there was no way to ask the runtime which faults exist. The values were reachable only by reading raise sites, and the only curated list of them lived outside this repo, in a hand-maintained conformance suite that could silently fall behind. `pipelex/validation_error_types.py` now holds the vocabulary in full and enumerates it as `VALIDATION_ERROR_TYPES`, so a consumer building coverage over the language surface — a test corpus, a client mapping faults onto its own UI — reads the registry instead of collecting strings from whichever diagnostics it happened to have seen. It is a **union of the enums the runtime already raises**, never a second list beside them: the two stage vocabularies plus a new `ValidationResidualErrorType` naming the one residual channel that had no enum of its own and rode an inline string. A member added to any of them is in the registry the moment it is declared. `ValidationErrorItem.error_type` is typed against their union, which is what makes the registry closed rather than merely documented — an unregistered string can no longer be constructed or parsed onto an item — and which publishes the vocabulary into the OpenAPI schema served for `/validate`, where the field was previously an open `string`. **No wire value changed**, including the dry-run residual's `DryRunError`: it keeps the exception-class spelling it has always had, because normalizing it would break every consumer that pins the string and would buy nothing an enumeration does not already give. Membership means a value is reachable on the wire, not that it is worth exercising — the advisory-only warning type and the two `unknown_*` fallbacks are in the registry and a coverage consumer excludes them on its own side, with a reason, rather than pruning the runtime's truth.-## [v0.49.0] - 2026-08-20### Addeddiff --git a/pyproject.toml b/pyproject.tomlindex 1f078af0d..94027bb09 100644--- a/pyproject.toml+++ b/pyproject.toml@@ -1,6 +1,6 @@[project]name = "pipelex"-version = "0.49.0"+version = "0.50.0"description = "Execute composable AI methods declared in the MTHDS open standard"authors = [{ name = "Evotis S.A.S.", email = "[email protected]" }]maintainers = [{ name = "Pipelex staff", email = "[email protected]" }]diff --git a/uv.lock b/uv.lockindex a2f12f3f8..2c2c40c02 100644--- a/uv.lock+++ b/uv.lock@@ -3303,7 +3303,7 @@ wheels = [[[package]]name = "pipelex"-version = "0.49.0"+version = "0.50.0"source = { editable = "." }dependencies = [{ name = "aiofiles" },