chore(deps): bump mcp-toolsets-runtime to 0.9.1 - #41
Merged
Merged
Conversation
Picks up the scaffold generating `async def` tools, so `mcp-toolset new` in this repo lays down the shape a tool doing I/O needs. 0.9.1 sits inside the existing `<0.10.0,>=0.9.0` pin, so this is the lock alone. `uv.lock` is a shared path, so it rebuilds and redeploys every toolset, which is what a runtime bump should do. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ciaransweet
force-pushed
the
chore/runtime-0.9.1
branch
from
September 14, 2026 09:17
082fae8 to
e2f90e2
Compare
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.
Picks up developmentseed/mcp-toolsets-runtime#135, which makes
mcp-toolset newgenerateasync deftools and a test that drives them throughainvoke. A toolset scaffolded in this repo now starts in the shape a tool doing I/O needs.0.9.1 sits inside the existing
<0.10.0,>=0.9.0pin, so this is the lock alone, with nopyproject.tomlchange. Unlike the 0.9.0 bump in #39, nothing here is breaking.uv.lockis a shared path, so this rebuilds and redeploys every toolset. That is the intended blast radius for a runtime bump, and it is why this is not folded into #40, which is test-only and would otherwise carry a full redeploy under a title that says nothing about it.🤖 Generated with Claude Code