From 90e588bf08d39fcfc6977a45c400f55b2e515e21 Mon Sep 17 00:00:00 2001 From: abrichr Date: Fri, 28 Aug 2026 14:28:59 -0400 Subject: [PATCH] docs: stop naming 2.0.2 as a shipped release PyPI serves 2.0.1 as the newest version, the newest tag is v2.0.1, and there is no v2.0.2 tag or GitHub Release. 2.0.2 is the version staged in the repository for the next release. Co-Authored-By: Claude Opus 5 --- docs/DISTRIBUTION.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/DISTRIBUTION.md b/docs/DISTRIBUTION.md index c9328ec..852d670 100644 --- a/docs/DISTRIBUTION.md +++ b/docs/DISTRIBUTION.md @@ -57,7 +57,7 @@ and [`../manifest.json`](../manifest.json). - **Name (reverse-DNS, official registry):** `io.github.OpenAdaptAI/openadapt-agent` - **Display name:** OpenAdapt Agent (openadapt-flow bridge) - **PyPI package:** `openadapt-agent` -- **Version:** `2.0.2` +- **Version:** `2.0.2` (staged in this repository; `2.0.1` is the newest version published to PyPI) - **Description:** Local bridge for governed openadapt-flow workflows and attended actions. - **Homepage / docs:** https://docs.openadapt.ai - **Repository:** https://github.com/OpenAdaptAI/openadapt-agent @@ -142,7 +142,10 @@ No secret is ever committed; these live only in repo Settings -> Secrets. ### 3.1 Decide the release version -The MCPB distribution release is `2.0.2`. Future releases must keep the package, +The version staged in this repository is `2.0.2`. It is not released yet: the +newest version on PyPI is `2.0.1`, the newest tag is `v2.0.1`, and there is no +`v2.0.2` tag and no GitHub Release. The commands below build the `2.0.2` +artifacts so a release can publish them. Future releases must keep the package, module, registry, and MCPB metadata versions synchronized. Set every future version in **four files that a CI test pins together**: