Repository navigation
fix: validate zero-argument tools and upgrade Console SDK to 0.7.0 - #122
Merged
Merged
Conversation
🟢 Tier S · Ready to merge
This change rejects unexpected arguments for hidden tools with no parameters and upgrades the Console SDK to 0.7.0. It updates the API-key catalog exclusions for renamed and newly added administration methods, and refreshes catalog tests and documentation without changing the public operator surface.
📂 Walkthrough · 8
Reviewed |
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.
Summary
appwrite-consolefrom 0.6.0 to 0.7.0 (>=0.7.0,<0.8) and refresh only that package inuv.lock.tables_db.create_cutoverand the six new organization project-key administration methods; remove obsolete exclusions for deleted SDK methods. The new Growth service remains OAuth-only.SDK release: https://github.com/appwrite/sdk-for-console-python/releases/tag/0.7.0
Compatibility review
Compared the complete 0.6.0 and 0.7.0 generated catalogs, reviewed the SDK breaking changes, and verified all services register successfully. SDK execution already uses keyword arguments, so optional-parameter reordering does not require call-site changes. Removed SDK methods disappear from the searchable catalog, and the renamed cutover method is advertised only for OAuth.
Synthetic response fixtures reproduce the field/type problems observed in Sentry; these are not production payload replays or proof of production resolution:
fallbackFile=nullpricingget_columnreceives a varchar columnColumnVarcharresourceId/resourceTypededicatedDatabase[]$permissionsflatten()MCP-A's unexpected keyword failure is addressed separately by the generic MCP validation fix in this PR. Upstream 500/503 failures are not addressed by this SDK upgrade.
Verification
On Python 3.12.8:
uv run --python 3.12 --group dev black --check src tests— passed.uv run --python 3.12 --group dev ruff check src tests— passed.uv run --python 3.12 --group dev pyright— passed, zero errors/warnings.uv run --python 3.12 python -m unittest discover -s tests/unit -v— 259 passed.uv run --python 3.12 --extra integration python -m unittest discover -s tests/integration -v— 24 discovered: 10 passed, 14 skipped. Passing coverage is docs/index integration; live Appwrite API/OAuth/operator end-to-end verification is blocked by missing credentials.git diff --check— passed.This is a backend change; no visual screenshots are applicable. Production error resolution must be verified after deployment.
Draft release note
Fixed
Updated
Compatibility
tables_db_cutover_migrationis nowtables_db_create_cutoverin the OAuth catalog.project_get_usage, andorganizations_cancel_downgradeare no longer advertised. Clients should rediscover tools rather than reuse removed names.