chore(deps): bump fastmcp from 3.4.7 to 4.0.3 - #222
Open
dependabot[bot] wants to merge 2 commits into
Open
dependabot[bot] wants to merge 2 commits into
dependabot[bot] wants to merge 2 commits into
Conversation
Bumps [fastmcp](https://github.com/PrefectHQ/fastmcp) from 3.4.7 to 4.0.3. - [Release notes](https://github.com/PrefectHQ/fastmcp/releases) - [Changelog](https://github.com/PrefectHQ/fastmcp/blob/main/docs/changelog.mdx) - [Commits](PrefectHQ/fastmcp@v3.4.7...v4.0.3) --- updated-dependencies: - dependency-name: fastmcp dependency-version: 4.0.3 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
PR author is in the excluded authors list. |
The bump changed pyproject.toml alone, so `uv sync --locked` failed before anything ran: the lockfile still resolved fastmcp 3.4.7. That was the whole of the Quality failure and most of the test failures. With the lock regenerated, fastmcp 4.0.3 runs this codebase almost unchanged -- 972 of 973 unit tests passed on the first attempt. The rest of this commit is the fallout from two API changes. MCP SDK v2 renamed the tool annotation fields to snake_case: readOnlyHint, destructiveHint, idempotentHint and openWorldHint become read_only_hint, destructive_hint, idempotent_hint and open_world_hint, and CallToolResult.structuredContent and .isError become structured_content and is_error. The camelCase spellings still resolve through a deprecation shim, so the suite passed on them, but they are gone from the type stubs: pyright reported 122 errors and mypy 98. All 165 occurrences are renamed here. The one camelCase spelling left is in a comment describing what AgentCat itself passes, which is still camelCase and would be wrong if changed. streamable_http_client now yields (read, write) rather than the v1 (read, write, get_session_id), so the integration client unpacks two. The one genuine test failure was a double rather than product code: the code-mode catalog's visibility check reads `component.meta`, and the fake backend tool was a SimpleNamespace without it. A component with no meta is visible, which is what that double always stood for -- fastmcp 4 just asks the question explicitly now. Verified: ruff, ruff format, pyright, mypy, `uv sync --locked`, the OpenAPI spec audit, and 973 unit tests all pass. The deprecation warnings the suite used to emit are gone as well.
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.
Bumps fastmcp from 3.4.7 to 4.0.3.
Release notes
Sourced from fastmcp's releases.
... (truncated)
Changelog
Sourced from fastmcp's changelog.
... (truncated)
Commits
7129236Add v4.0.3 changelog entries (#5007)f79bc82chore: Update SDK documentation (#4945)6e0859ffix task timing field serialization (#5003)855cb7aClarify release title history lookup (#5006)6236ac1Clean up unfinished Monty callbacks (#5005)6c2fbe7docs: attribute the back-channel removal to SEP-2322/2575, not SEP-2577 (#4988)e68baccperf: avoid duplicate startup for mixed-era backends (#4971)032b9f6fix: don't infer an output schema for unconstrained sequences (#4999)75d50ffci: deploy docs through Mintlify's admin API and wait for a verdict (#4996)a338cfbdocs: point What's New at the changelog for later releases (#4992)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)