Skip to content

docs: stop naming 2.0.2 as a shipped release - #37

Merged
abrichr merged 1 commit into
mainfrom
claims-fix/measured-results
Aug 28, 2026
Merged

docs: stop naming 2.0.2 as a shipped release#37
abrichr merged 1 commit into
mainfrom
claims-fix/measured-results

Conversation

@abrichr

@abrichr abrichr commented Aug 28, 2026

Copy link
Copy Markdown
Member

docs/DISTRIBUTION.md said "The MCPB distribution release is 2.0.2" and listed 2.0.2 as the registry version. Nothing with that number has shipped.

What is actually published:

  • PyPI openadapt-agent: 2.0.0 and 2.0.1, newest is 2.0.1
  • git tags: v0.1.0, v2.0.0, v2.0.1. No v2.0.2.
  • GitHub Releases: none

2.0.2 is the version staged in the repository for the next release, and the pack commands later in the file correctly build 2.0.2 artifacts. The two lines that read as a shipped-release claim now say which is which.

No version constant changed, so the four-file pin in tests/test_distribution.py is untouched. pytest passes (98 tests) and ruff check is clean.

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 <noreply@anthropic.com>
@abrichr
abrichr merged commit 3da4434 into main Aug 28, 2026
7 checks passed
@abrichr
abrichr deleted the claims-fix/measured-results branch August 28, 2026 18:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant