chore(deps): bump fastmcp constraint to >=3.0.0#191
Merged
stickerdaniel merged 1 commit intomainfrom Mar 4, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR aligns the declared fastmcp dependency floor with the already-locked FastMCP 3.x version to prevent accidental resolution to FastMCP v2 (per issue #190).
Changes:
- Bump
fastmcpdependency constraint inpyproject.tomlfrom>=2.14.0to>=3.0.0. - Update
uv.lockproject metadata (requires-dist) to match the newfastmcp>=3.0.0constraint.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
pyproject.toml |
Raises the minimum FastMCP version requirement to v3. |
uv.lock |
Updates the recorded requires-dist constraint for FastMCP to >=3.0.0. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Owner
Author
Merge activity
|
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
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.

Lock file already has 3.1.0 since #166; align pyproject.toml
floor to prevent accidental downgrades to v2.
Resolves: #190
Greptile Summary
This PR tightens the
fastmcpminimum version constraint from>=2.14.0to>=3.0.0inpyproject.toml(and the correspondinguv.lockmetadata), preventing any future resolver from backtracking to the incompatible v2 series. The lock file has already been pinningfastmcp==3.1.0since PR #166, so there is no runtime impact — this is purely a spec/metadata alignment.pyproject.toml:fastmcpfloor raised to>=3.0.0uv.lock:package.metadata.requires-distupdated to match; the resolved package entry (3.1.0) is unchanged<4.0.0) is set, which is consistent with the project's existing open-ended constraints for all other dependenciesConfidence Score: 5/5
3.1.0before this PR; the only change is raising the declared floor to match. Both modified lines are trivially correct, consistent with each other, and have no side-effects on the installed environment.Important Files Changed
fastmcpfloor constraint from>=2.14.0to>=3.0.0, aligning with the already-resolved version in the lock file.>=3.0.0specifier; the resolvedfastmcpversion (3.1.0) was already correct and unchanged.Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A["pyproject.toml\nfastmcp >=3.0.0"] -->|uv resolves| B["uv.lock\nfastmcp 3.1.0 (pinned)"] B --> C["Installed environment\nfastmcp 3.1.0"] D["Old constraint\nfastmcp >=2.14.0"] -. "could resolve to" .-> E["fastmcp 2.x\n(incompatible)"] style D fill:#f9d0d0,stroke:#c00 style E fill:#f9d0d0,stroke:#c00 style A fill:#d0f0d0,stroke:#060 style B fill:#d0f0d0,stroke:#060 style C fill:#d0f0d0,stroke:#060Last reviewed commit: 7d2363e