Pin appwrite below 16 to avoid tablesdb startup failures#41
Merged
ChiragAgg5k merged 1 commit intomainfrom Apr 11, 2026
Merged
Conversation
Greptile SummaryPins the Confidence Score: 5/5Safe to merge — minimal, well-scoped dependency pin with no code changes. Both changed files contain only the intended constraint update; the lock file's resolved package version is unaffected and already satisfies the new bound. No logic or security concerns introduced. No files require special attention. Important Files Changed
Reviews (1): Last reviewed commit: "Pin appwrite below 16" | Re-trigger Greptile |
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
Pin the Python Appwrite SDK to
<16.This keeps
mcp-server-appwriteon the last pre-strict-typing SDK line and avoids theTablesDB.list()startup failure some users are hitting against Appwrite Cloud.Why
mcp-server-appwrite0.4 currently performs a minimal startup probe againsttables_dbby callingTablesDB.list().For older Python SDK versions, that call returned a raw
dict, so malformed nested response values from/tablesdbwere tolerated.Starting with
appwrite16.0.0, the Python SDK switchedTablesDB.list()to parse into a typedDatabaseList. That makes the startup probe fail fast when Appwrite Cloud returns malformed nested values such as:databases[*].policies[*].status = ""databases[*].archives[*].documentSecurity = ""We verified the version boundary while investigating:
15.3.0still returnsDict[str, Any]16.0.0returns typedDatabaseList16.0.0and17.0.0both fail on the malformed synthetic/tablesdbpayloadPinning to
<16is the narrowest dependency change that restores the previous behavior without changing the server code path.Changes
pyproject.tomlto requireappwrite>=13.4.1,<16uv.lockmetadata to match the new constraintTesting
uv lockuv run python -m unittest discover -s tests/unit -p 'test_server.py'Notes
There is no linked issue number in this repo for this change yet. This is a compatibility pin to avoid known startup failures until the upstream response mismatch is resolved or the server is updated to handle it differently.