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

Louis Choquel52a5c9428023
diff --git a/.claude/skills/release/SKILL.md b/.claude/skills/release/SKILL.md
index 2ab103c89..367a8cc4e 100644
--- a/.claude/skills/release/SKILL.md
+++ b/.claude/skills/release/SKILL.md
@@ -44,7 +44,19 @@ Run `make agent-check`. This is the gate — if it fails, stop and report the
errors so they can be fixed before retrying. Do not proceed past this step on
failure.
-### 4. Finalize the changelog
+### 4. Ensure we're on the right branch
+
+The release branch must be named `release/vX.Y.Z` where X.Y.Z is the **new**
+version. All file modifications (changelog, version bump, lock, badge) must
+happen on this branch.
+
+- If already on `release/vX.Y.Z` matching the new version, stay on it.
+- If on `dev`, `main`, or any other branch, create and switch to
+ `release/vX.Y.Z` from the current HEAD.
+- If on a `release/` branch for a **different** version, warn the user and ask
+ how to proceed.
+
+### 5. Finalize the changelog
Add a new version entry at the top of the changelog for the release.
@@ -71,18 +83,18 @@ Add a new version entry at the top of the changelog for the release.
...
```
-### 5. Bump the version in pyproject.toml
+### 6. Bump the version in pyproject.toml
Edit `pyproject.toml` line 3 to the new version string. Only change the version
field — don't touch anything else.
-### 6. Lock dependencies
+### 7. Lock dependencies
Run `make li` to regenerate `uv.lock` and reinstall. This ensures the lockfile
reflects the new version in `pyproject.toml`. If this step fails, stop and
report the error.
-### 7. Update the test count badge
+### 8. Update the test count badge
Run `make test-count` to get the current number of tests. Then update
`.badges/tests.json` — set the `"message"` field to the count returned by
@@ -91,17 +103,6 @@ Run `make test-count` to get the current number of tests. Then update
After updating, run `make check-test-badge` to verify the badge matches. If it
fails, re-check the count and fix the badge file.
-### 8. Ensure we're on the right branch
-
-The release branch must be named `release/vX.Y.Z` where X.Y.Z is the **new**
-version.
-
-- If already on `release/vX.Y.Z` matching the new version, stay on it.
-- If on `dev`, `main`, or any other branch, create and switch to
- `release/vX.Y.Z` from the current HEAD.
-- If on a `release/` branch for a **different** version, warn the user and ask
- how to proceed.
-
### 9. Commit and push
Stage all release-related changes. This includes at minimum `pyproject.toml`,
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 931eb69ee..e07cfa61a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,13 @@
# Changelog
+## [v0.20.9] - 2026-03-16
+
+### Changed
+
+- Reporganize documentation site architecture and navigation.
+- Add SEO meta descriptions to all doc pages.
+- Redesign README: lead with value, collapse details.
+
## [v0.20.8] - 2026-03-13
- Add `needs_model_specs=True` to agent CLI run and models commands.
diff --git a/pyproject.toml b/pyproject.toml
index 86f408ce9..7e4218acf 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -1,6 +1,6 @@
[project]
name = "pipelex"
-version = "0.20.8"
+version = "0.20.9"
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 3991145f9..25c919c83 100644
--- a/uv.lock
+++ b/uv.lock
@@ -3420,7 +3420,7 @@ wheels = [
[[package]]
name = "pipelex"
-version = "0.20.8"
+version = "0.20.9"
source = { editable = "." }
dependencies = [
{ name = "aiofiles" },