fix: allow fastmcp 4.0.3+ / mcp 2.2.0+ and fix the OAuth test for mcp 2 (#37) #39
Loading…
Reference in a new issue
No description provided.
Delete branch "v6.7.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Corrects #38. That PR bounded
fastmcp<4/mcp<2, but production already runs OmniMem 6.7.1 on fastmcp 4.0.3 / mcp 2.2.0 without trouble, so the bound pointed CI and the next image build at older versions than the ones in use.What actually broke on mcp 2
Only a test. In mcp 2,
OAuthClientInformationFull.client_idis a requiredstr, and amode="before"validator stripsnulland""at parse time, so the model can't be built without an id. mcp 2's registration handler assignsstr(uuid4())before calling the provider, so a real registration always arrives with one.test_register_and_getbuilt a client withclient_id=None, which is the only thing that failed.Change
fastmcp>=4.0.3,<5andmcp>=2.2.0,<3: floor at the production versions, ceiling at the next major so the next breaking release is adopted deliberately. mcp stays listed because fastmcp's metadata doesn't declare ittest_register_and_getregisters a client with its id already assigned, as mcp 2 delivers ittest_register_generates_an_id_when_blankreaches the provider's generate-if-missing fallback throughmodel_copy(skips validation)[6.7.2] - Unreleasedrewritten to matchVerified
The Test Coverage job's exact steps on a clean Python 3.12 install with no cache:
memory/andtools/module at 100%The v6.7.1 images don't need rebuilding: they run the same versions this PR now declares.
🤖 Generated with Claude Code
https://claude.ai/code/session_01HWqtyPdN5MHxqoVM3Sj9xD