docs: drop alpha status messaging from READMEs and package metadata - #231
Merged
Conversation
Removes the "Alpha Status" bullet and the "Alpha Status (0.x.y)" section from the root README, the preview banner from packages/a2a, and bumps the Development Status classifier from "3 - Alpha" to "4 - Beta" across all packages so PyPI stops rendering the alpha badge. The 0.x versioning and "When Will Packages Reach 1.0?" sections are left alone; they describe semver behavior rather than maturity.
jerriclynsjohn
approved these changes
Aug 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Drops the alpha messaging from the READMEs and package metadata, matching the "early access" wording already pulled from the website.
### Alpha Status (0.x.y)sectionpackages/a2a/README.mdpyproject.toml: classifier goes from"Development Status :: 3 - Alpha"to"Development Status :: 4 - Beta"I left the
0.x.yversioning section and "When Will Packages Reach 1.0?" alone. Those describe semver behavior rather than maturity, so they're still accurate.Two things worth knowing:
docsisn't in any package'schangelog_pattern, so this triggers no bump and no publish. The new classifier only reaches PyPI on each package's next real release.keycardai-mcpis already at 2.0.0, which makes "When Will Packages Reach 1.0?" stale for at least one package. Didn't touch it here.