chore(deps)!: bump mcp-toolsets-runtime to 0.5.0, move to the [web] extra - #24
Merged
Conversation
…xtra 0.5.0 split the Chainlit host out of `[agent]`, so anything wanting `build_agent`, `run_turn` or the `mcp_agent.host` helpers no longer installs a UI framework it never imports. Two declarations here run Chainlit and move to `[web]`: - the root dependency, which is what the dev environment uses for `mcp-agent-web` and `mcp-agent install-elements`; - the `chat` group, which is Dockerfile.chat. The `index` group and the toolset images are unaffected — they never asked for an extra, and the toolset image syncs with `--package`, so the root dependency never reaches it. Verified by syncing all three into throwaway venvs: `chat` has chainlit and imports `mcp_agent.web`; `index` and `hello` have no chainlit and import `mcp_runtime.index` and `mcp_runtime.server` respectively. Also picks up 0.5.0 declaring httpx as a base dependency. `mcp_runtime.index` imports it and `mcp-index` is a base entry point, so the index image had been relying on it arriving transitively through mcp. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Runtime 0.5.0 split the Chainlit host out of
[agent]: anything wantingbuild_agent,run_turnor themcp_agent.hosthelpers no longer installs a UIframework it never imports.
[web]is[agent]plus Chainlit.Two of this repo's declarations actually run Chainlit, and only those move:
[agent][web]mcp-agent-webandmcp-agent install-elementschatgroup[agent][web]indexgroupuv sync --package <toolset>, so root deps never reach themThat last row is the one worth checking rather than assuming — if the toolset
images did pick up the root dependency,
[web]there would put Chainlit intoevery deployed service.
Verified
Each of the three install paths synced into its own venv:
--only-group chatmcp_agent.webok--only-group indexmcp_runtime.indexok--package hellohello.tools,mcp_runtime.serverokPlus
./scripts/lintand./scripts/test(18 passed).Also arriving with 0.5.0
httpx is now a base dependency of the runtime.
mcp_runtime.indeximports it atmodule level and
mcp-indexis a base entry point, so the index image had beenrelying on it coming in transitively through
mcp.uv.lockis a shared path, so this redeploys every toolset.🤖 Generated with Claude Code