Skip to content

chore(deps): Update mcp requirement from >=2.2.0 to >=2.3.0 in /compose-configs/egeria-freshstart/PyegeriaWebHandler #616

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dependabot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): Update mcp requirement from >=2.2.0 to >=2.3.0 in /compose-configs/egeria-freshstart/PyegeriaWebHandler #616

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion compose-configs/egeria-freshstart/PyegeriaWebHandler/requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ email-validator
loguru
rich
click
mcp >=2.2.0 # This directory's own mcp_server.py (source-fixed 2026-07-31: FastMCP->mcp.server.mcpserver.MCPServer, dropped the dead server.settings.transport_security assignment) is the only mcp server this container actually imports/runs (pyegeria_handler.py:198 does `from mcp_server import server`) -- confirmed pyegeria's own pyegeria/core/mcp_server.py is NOT imported anywhere in this container (no reference to pyegeria.core.mcp_server or the `pyegeria-mcp` console script here), so this pin is independent of whether pyegeria has published its own mcp_server.py fix yet. Previously left at <2.0.0 out of caution for that unrelated file, which just meant this container's own already-migrated code had no matching mcp installed -- ModuleNotFoundError: No module named 'mcp.server.mcpserver'. If this container ever starts importing pyegeria.core.mcp_server directly, re-check that it's compatible with mcp>=2.0.0 (i.e. a pyegeria release containing the mcp_server.py fix) before relying on this pin.
mcp >=2.3.0 # This directory's own mcp_server.py (source-fixed 2026-07-31: FastMCP->mcp.server.mcpserver.MCPServer, dropped the dead server.settings.transport_security assignment) is the only mcp server this container actually imports/runs (pyegeria_handler.py:198 does `from mcp_server import server`) -- confirmed pyegeria's own pyegeria/core/mcp_server.py is NOT imported anywhere in this container (no reference to pyegeria.core.mcp_server or the `pyegeria-mcp` console script here), so this pin is independent of whether pyegeria has published its own mcp_server.py fix yet. Previously left at <2.0.0 out of caution for that unrelated file, which just meant this container's own already-migrated code had no matching mcp installed -- ModuleNotFoundError: No module named 'mcp.server.mcpserver'. If this container ever starts importing pyegeria.core.mcp_server directly, re-check that it's compatible with mcp>=2.0.0 (i.e. a pyegeria release containing the mcp_server.py fix) before relying on this pin.

# Demo-mode dependencies
sqlalchemy
Expand Down
Loading