fix: bound fastmcp and mcp below their next majors (#37) #38
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?
Fixes the failing Test Coverage job on main (#37).
Cause
mcp_server/requirements.txthadfastmcp>=2.13.0with no ceiling, so a fresh install resolved fastmcp 4.0.3 / mcp 2.2.0, two majors past the fastmcp 3.4.7 / mcp 1.29.0 that 6.7.1 was tested on. mcp 2 madeOAuthClientInformationFull.client_idrequired, which failedtests/test_oauth.py::TestClientRegistration::test_register_and_get. Nothing in OmniMem had changed.Change
fastmcp>=2.13.0,<4andmcp>=1.24.0,<2. mcp is bounded explicitly because fastmcp's metadata doesn't declare it, so a fastmcp pin alone can't be relied on to hold mcp backtools/briefing.py _skill_source_keys(empty skill row, store error while reading manifests), sotools/is back at 100%[6.7.2] - UnreleasedVerified
Ran the job's exact steps (uv venv on Python 3.12, the same pip installs,
pytest --cov=memory --cov=tools --cov-report=xml,genbadge) against a clean install with no cache:memory/andtools/module at 100%Follow-up
Images built from the v6.7.1 tag resolved the unbounded versions and should be rebuilt once this is on main. Moving to fastmcp 4 is separate work.
🤖 Generated with Claude Code
https://claude.ai/code/session_01HWqtyPdN5MHxqoVM3Sj9xD