Repository navigation
chore(antd-mcp): require antd 0.3.0 now that it is on PyPI - #387
Merged
Merged
Conversation
antd 0.3.0 (PyPI, 2026-10-22) is the first SDK release with the pointer and manifest APIs the pointer and manifest tools call. #386 could only widen the cap (<0.4) because the security audit resolves against PyPI, which didn't have 0.3.0 yet. The import guards in server.py, manifests.py and errors.py stay for installs that bypass the floor. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Follow-up to #386. antd 0.3.0 is now on PyPI (published 2026-10-22 from
antd-py-v0.3.0). It's the first SDK release with the pointer and manifest APIs that antd-mcp's pointer and manifest tools call, so the floor moves up to it:antd-mcp/pyproject.toml:antd[rest]>=0.2.0,<0.4→antd[rest]>=0.3.0,<0.4, with the comment rewritten to match.server.py,manifests.py,README.mdand thetest_errors_compat.pydocstring now say "0.3.0 or later" instead of "newer than 0.2.0".#386 could only widen the cap. The security audit's
uv pip compileresolves eachpyproject.tomlagainst PyPI, and 0.3.0 wasn't published then.The import guards stay. An install that bypasses the floor (e.g.
--no-deps) still starts and serves the other tools, and the compat tests still simulate a 0.2.0 SDK.Checked locally:
uv pip compile antd-mcp/pyproject.toml --all-extrasresolvesantd==0.3.0from PyPI.-e ./antd-py[rest] -e ./antd-mcp[test]) gives 123 passed, 2 skipped.antd-mcp stays 0.1.0 and isn't published.
🤖 Generated with Claude Code