[AAASM-4840] 📝 (examples): Sync README dependency version floors to manifest pins#336
Merged
Merged
Conversation
Each README's stated framework version floor contradicted the actual pyproject pin, so following the documented floor did not satisfy the manifest. Align the prose to the pins (source of truth), unchanged: agno >=2.7.2, haystack-ai >=2.31.0,<3.0, semantic-kernel >=1.39.4, smolagents >=1.26.0,<2.0.0, pydantic-ai >=2.9.0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Contributor
Author
🤖 Claude Code — PR reviewScope (AAASM-4840, MED): ✅ 5 README version floors synced to the manifest pins; no pin changed.
|
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
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.



What changed
Each of five Python example READMEs stated a framework dependency version floor that contradicted the actual pin in its
pyproject.toml, so a user following the documented floor could install a version the manifest rejects. This syncs the README prose to the pins (the source of truth) — no pin was changed:pydantic-ai>=2.9.0>=0.3.0→>=2.9.0agno>=2.7.2>= 2.0.0→>= 2.7.2haystack-ai>=2.31.0,<3.0>= 2.0.0, < 3.0→>= 2.31.0, < 3.0semantic-kernel>=1.39.4>= 1.36.0→>= 1.39.4smolagents>=1.26.0,<2.0.0>= 1.0, < 2.0→>= 1.26.0, < 2.0.0Docs-only; no dependency pins, code, or generated
sdk-installblocks were touched.Related ticket
Closes AAASM-4840
Jira: https://lightning-dust-mite.atlassian.net/browse/AAASM-4840
How to verify
For each example, the README's stated floor now matches the
>=(and upper bound) in itspython/<example>/pyproject.toml:Checklist
[AAASM-XXXX] <GitEmoji> (<scope>): <summary>.envfiles committedREADME.mdwith prerequisites and run instructions🤖 Generated with Claude Code