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.

docs/After-2026-09-14-excludes-v0580 · L-260920-4a273a (#1221)

Louis Choqueld9292e5f3bc4
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 00be6083f..47df8eaad 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -25,6 +25,8 @@
- **A remote fetch honours a timeout again**: `fetch_file_from_url_httpx` passed its `request_timeout` straight to httpx, and httpx reads an explicit `timeout=None` — the parameter's own default — as *no timeout at all* rather than as its client default. Every caller that did not name one therefore had no timeout, so a hanging server blocked the caller indefinitely and the `TimeoutException` branch that raises a caller-facing `RemoteFileFetchError` was unreachable. The helper now passes httpx's `USE_CLIENT_DEFAULT` sentinel where no timeout was asked for.
- **A manifold error on the native routes keeps its request id under the gateway's pipelex-spelled trace header**: `extract_manifold_metadata` reads the gateway's trace id from `x-pipelex-trace-id` before the inherited `x-portkey-trace-id`, still preferring a provider's own `x-request-id` over both. The gateway emits the two spellings with the same value today, so nothing changes yet; once it drops the vendor one, such an error whose provider sent no `x-request-id` keeps a request id instead of reporting none. `extract_gateway_metadata` is unchanged and still reads the vendor spelling alone — it serves the Portkey cloud and the manifold image path, which travels on `portkey_ai` and keeps that spelling until it is ported off the SDK.
+- **The License page names the versions the Elastic License 2.0 starts at**: the page said ELv2 applies "for every version released after 2026-09-14", which left the first ELv2 releases outside the boundary it drew, since all three were released on that very day. It now names them instead of dating them — `pipelex` from v0.58.0 onward, `pipelex-api` from v0.24.0 onward and `@pipelex/mcp` from v0.15.0 onward — and spells out the last MIT version of each.
+
## [v0.60.0] - 2026-09-19
### Changed
diff --git a/docs/license.md b/docs/license.md
index 10748bc65..ca9a18838 100644
--- a/docs/license.md
+++ b/docs/license.md
@@ -13,7 +13,7 @@ This section explains how we, the maintainers of Pipelex, read the license, so t
### What does the license cover?
-The Elastic License 2.0 is a source-available license: you may use, copy, distribute, modify and build on the software, within the limitations and conditions it sets. It applies to `pipelex` (the Python runtime), `pipelex-api` (the runner API server) and `@pipelex/mcp` (the MCP server), for every version released after 2026-09-14. Every earlier version of them stays under the MIT license it was released with.
+The Elastic License 2.0 is a source-available license: you may use, copy, distribute, modify and build on the software, within the limitations and conditions it sets. It applies to `pipelex` (the Python runtime) from v0.58.0 onward, to `pipelex-api` (the runner API server) from v0.24.0 onward and to `@pipelex/mcp` (the MCP server) from v0.15.0 onward — the three versions released on 2026-09-14. Every earlier version of them stays under the MIT license it was released with: `pipelex` up to and including v0.57.0, `pipelex-api` up to and including v0.23.0, and `@pipelex/mcp` up to and including v0.14.0.
The other Pipelex repositories, such as the SDKs, the starters and the plugins, keep their own licenses, and so does the MTHDS language standard.