Skip to content

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.64.0

thomashebrardb36b0c4b3b7a
diff --git a/.badges/tests.json b/.badges/tests.json
index 7719ace03..ba62ab407 100644
--- a/.badges/tests.json
+++ b/.badges/tests.json
@@ -1,7 +1,7 @@
{
"schemaVersion": 1,
"label": "tests",
- "message": "11996",
+ "message": "12034",
"color": "blue",
"cacheSeconds": 300
}
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 308729977..c321186a5 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,6 +1,6 @@
# Changelog
-## [Unreleased]
+## [v0.64.0] - 2026-09-24
### Added
@@ -8,9 +8,9 @@
### Changed
-- **A run's `analytics_groups` is renamed `extras` (Breaking)**: the base library no longer names an analytics concept in its run model or its job-preparation signatures. `RunMetadata.analytics_groups`, the runtime-bridge payload's `analytics_groups`, and the `analytics_groups` parameter of `pipeline_run_setup`, `prepare_pipe_job`, `PipelexKernel.make` and `PipelexRunner` are now `extras`: an opaque `dict[str, str]` of labels the host attaches to a run, which the library never reads by name. The module `pipelex.system.analytics_groups` is now `pipelex.system.run_extras`, with `validate_run_extras`, `RUN_EXTRAS_KEY_PATTERN`, `RUN_EXTRAS_VALUE_PATTERN` and `RUN_EXTRAS_MAX_ENTRIES`, and the span attribute `pipelex.run.analytics_groups` is now `pipelex.run.extras` (`PipelexSpanAttr.RUN_EXTRAS`). Behaviour is unchanged: the mapping is validated where it enters under the same bounds, and telemetry still forwards it whole as the PostHog groups of each capture. There is no alias; a host passing `analytics_groups` must pass `extras` instead.
+- **A run's `analytics_groups` is renamed `extras` (Breaking)**: the base library no longer names an analytics concept in its run model or its job-preparation signatures. `RunMetadata.analytics_groups`, `PipelexPipeRunInput.analytics_groups` on the runtime-bridge payload, and the `analytics_groups` parameter of `pipeline_run_setup`, `prepare_pipe_job`, `PipelexKernel.make` and the `PipelexMTHDSProtocol` constructor are now `extras`: an opaque `dict[str, str]` of labels the host attaches to a run, which the library never reads by name. Behaviour is unchanged: the mapping is validated where it enters under the same bounds, and telemetry still forwards it whole as the PostHog groups of each capture. **Migration:** rename every `analytics_groups=` argument and field to `extras`; there is no alias, and while the functions and `PipelexPipeRunInput` refuse the old name, `RunMetadata` silently ignores it, so a missed rename there drops the groups without an error. Import from `pipelex.system.run_extras` instead of `pipelex.system.analytics_groups`, calling `validate_run_extras` instead of `validate_analytics_groups`, with the bounds now named `RUN_EXTRAS_KEY_PATTERN`, `RUN_EXTRAS_VALUE_PATTERN` and `RUN_EXTRAS_MAX_ENTRIES`. A dashboard, query or exporter reading the span attribute `pipelex.run.analytics_groups` must read `pipelex.run.extras` (`PipelexSpanAttr.RUN_EXTRAS`) instead.
- **Pipelex's own telemetry stream receives the run's `user_id` as it is**: the Gateway stream sent a one-way digest of the caller taken inside the Gateway-key hash, and carried a `deployment` group instead of the run's own groups. It now resolves identity like the operator's identified stream — the run's `user_id` is the PostHog `distinct_id` and its `extras` ride the groups facet — so a host's events and the runtime's land on the same person and the same organization. The `NAMESPACED` identity policy and the `deployment` group type are removed. Anything that names no caller still reports under the Gateway-key hash.
-- **`BundleValidatorProtocol.validate_bundles` requires `caller_identity` (Breaking)**: a validator is handed who asked for the validation, `None` meaning nobody, so a hosted `/validate` attributes its telemetry to its caller. Every validator implementation must accept the argument, and a host must pass it — `caller_identity=self.caller_identity` from a `PipelexMTHDSProtocol` runner. `validate_bundles_in_process`, `validate_bundle`, `dry_run_pipe_in_process` and the `BundleValidator` sweep methods gain an optional `caller_identity` of their own.
+- **`BundleValidatorProtocol.validate_bundles` requires `caller_identity` (Breaking)**: a validator is handed who asked for the validation, `None` meaning nobody, so a hosted `/validate` attributes its telemetry to its caller. `validate_bundles_in_process`, `validate_bundle`, `dry_run_pipe_in_process` and the `BundleValidator` sweep methods gain an optional `caller_identity` of their own. **Migration:** every plugin implementing `BundleValidatorProtocol` must add a keyword-only `caller_identity: CallerIdentity | None` parameter to `validate_bundles` and pass it on to the sweep it runs, carrying it to the worker when the validation is dispatched. Every host calling `validate_bundles` must now pass it explicitly: `caller_identity=self.caller_identity` from a `PipelexMTHDSProtocol` runner, or `None` for a validation nobody in particular asked for.
### Fixed
diff --git a/pyproject.toml b/pyproject.toml
index 8ddaf95ea..0466e008b 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -1,6 +1,6 @@
[project]
name = "pipelex"
-version = "0.63.0"
+version = "0.64.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.lock
index aea169972..fcc8bc0c8 100644
--- a/uv.lock
+++ b/uv.lock
@@ -3303,7 +3303,7 @@ wheels = [
[[package]]
name = "pipelex"
-version = "0.63.0"
+version = "0.64.0"
source = { editable = "." }
dependencies = [
{ name = "aiofiles" },