Skip to content

chore(fetch): raise the Python floor to 3.11.5 so the lock drops soupsieve 2.10 - #5567

Merged
cliffhall merged 1 commit into
v2/mainfrom
v2/chore/5546-fetch-python-floor-soupsieve
Nov 18, 2026
Merged

cliffhall merged 1 commit into
v2/mainfrom
v2/chore/5546-fetch-python-floor-soupsieve

Conversation

@cliffhall

Copy link
Copy Markdown
Member

Closes #5546

Description

Raises mcp-server-fetch's Python floor from >=3.10 to >=3.11.5 and re-locks, so src/fetch/uv.lock no longer holds a soupsieve inside any of the three advisory ranges on #5546.

This is a floor bump for the published mcp-server-fetch package (Python servers carry no changeset, so the release notes need to call it out by hand): the next release will not install on Python 3.10 through 3.11.4.

Why the floor and not just the lock: every soupsieve release patched against these advisories (3.0.2 and up, including 4.0.0) declares requires-python >=3.11.5. With fetch at >=3.10, uv forked the lock: 4.0.1 for >= 3.11.5 and the vulnerable 2.10 for everything older. uv lock --upgrade-package soupsieve cannot remove that fork, and the issue's fallback (constraint-dependencies = ["soupsieve>=4.0.0"]) makes resolution fail for the same reason. The maintainer chose to raise the floor.

  • src/fetch/pyproject.toml: requires-python = ">=3.11.5"; the 3.10 classifier becomes 3.11 (git and time list their floor's minor the same way).
  • src/fetch/uv.lock: re-locked with uv lock. No package version is added or bumped. Twelve entries are removed, all of them the old floor's: the soupsieve 2.10 fork, the 3.10-only backports (tomli, exceptiongroup, backports-asyncio-runner), the older half of each fork that existed only for Python < 3.11.5, and the cp310 wheels.
  • src/fetch/README.md: states the requirement under Installation.
  • AGENTS.md: the "Python >= 3.10 for the Python servers" rule now names fetch's exception and why, so it stays true of the repository.

.python-version (3.11), the Dockerfile (3.12) and CI (which reads .python-version) already run above the new floor and are unchanged. git and time stay at >=3.10.

Server Details

  • Server: fetch
  • Changes to: packaging metadata (requires-python), lockfile, README. No tools, prompts or behaviour.

Motivation and Context

#5546: three Dependabot advisories on soupsieve (two high, one medium), a runtime transitive dependency through beautifulsoup4.

How Has This Been Tested?

No client-observable surface changes, so these are targeted probes:

  • The lock holds one soupsieve, outside every range: grep -A1 'name = "soupsieve"' src/fetch/uv.lock gives a single entry, 4.0.1 (ranges on the issue: <= 2.10, >= 0.4, <= 2.10, < 4.0.0).
  • The alert sweep's dry run against this branch (GITHUB_REPOSITORY=modelcontextprotocol/servers node scripts/dependabot-alerts.mjs --dry-run, writes nothing) reports: cleared #5546: every installed copy is out of range (4.0.1).
  • The fetch suite on the new floor exactly: uv run --frozen --python 3.11.5 pytest in src/fetch, on CPython 3.11.5 with soupsieve 4.0.1: 573 passed. The same suite on the default interpreter (3.11.17): 573 passed. pyright: 0 errors; ruff check and ruff format --check: clean.
  • Below the floor is refused: uv sync --locked --python 3.10 fails with "incompatible with the project's Python requirement: >=3.11.5".
  • Lock churn is removals only: comparing the (name, version) set of the lock before and after gives 12 removed, 0 added.
  • npm run local:gate exits 0, including the boot smoke over stdio and Streamable HTTP and the interface diff ("No interface changes detected" for fetch).

Breaking Changes

Yes, for users running mcp-server-fetch on Python 3.10 through 3.11.4: they need Python 3.11.5 or newer. uvx users are unaffected (uv fetches a suitable interpreter), as are Docker users (the image is on 3.12). No client configuration changes.

Types of changes

  • Bug fix (dependency security update)
  • New feature
  • Breaking change (Python floor of the published package)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation (not applicable: no protocol surface is touched)
  • My changes follow MCP security best practices
  • I have updated the server's README accordingly
  • I have added a changeset (not applicable: a Python server; the floor bump is called out above for the release notes)
  • I have tested this with an LLM client (not applicable: no tool, prompt or behaviour changes; the interface diff is empty and the gate's boot smoke passes)
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling (not applicable: no code changes)
  • I have documented all environment variables and configuration options (not applicable: none added)

🤖 Generated with Claude Code

…0 from the lock

No soupsieve release patched against GHSA-6655-6qjp-jx7x,
GHSA-7g44-g9rc-x53w and GHSA-mmhr-3c5m-f64f supports Python below 3.11.5,
so with requires-python >=3.10 the lock kept a vulnerable 2.10 fork for
older interpreters. Raising the floor collapses the fork onto 4.0.1; the
re-lock removes only what the old floor needed and bumps nothing.

Closes #5546

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Signed-off-by: cliffhall <cliff@futurescale.com>
@cliffhall cliffhall added the v2 label Nov 18, 2026
@changeset-bot

changeset-bot Bot commented Nov 18, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 31a7275

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions

Copy link
Copy Markdown
Contributor

fetch: MCP interface diff

Base: b9a69dcba9a7 (Merge pull request #5563 from modelcontextprotocol/v2/fix/5560-memory-stale-lock-race)
Head: the build in this checkout, at 80cfa4d9b3f3 (Merge 31a7275 into b9a69dc)

Diffed because it was named (--server).

✅ No interface changes detected.

Tools Prompts Resources Resource templates
Base 1 1 0 0
Head 1 1 0 0

Updated by this run for 31a72754c3b6048624929fad517a6261479af152.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

There are no active review issues for the Python baseline and dependency update.

No open issues 🎉

What changed in this PR

Raises the fetch reference server’s minimum Python version to 3.11.5 so its lockfile can drop vulnerable soupsieve 2.10, addressing #5546. This ends support for Python 3.10 through 3.11.4 without changing the server’s MCP interface.

Changes:

  • Updates package metadata to require Python 3.11.5 or newer.
  • Removes older-Python dependency variants and wheels, leaving soupsieve 4.0.1.
  • Documents the new requirement and fetch’s exception to the repository-wide Python baseline.
File Description
src/​fetch/​uv.lock Removes vulnerable soupsieve and dependencies specific to older Python versions.
src/​fetch/​README.md Documents the minimum Python version for installation.
src/​fetch/​pyproject.toml Raises requires-python and updates the Python classifier.
AGENTS.md Records fetch’s Python baseline exception and its rationale.

Review effort: Balanced

@cliffhall

Copy link
Copy Markdown
Member Author

Copilot round 1: clean. The review recommends approval, with no inline comments and no suppressed findings, so the loop ends here on the first clean round. Nothing was declined and nothing was pushed in response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

chore(deps): bump soupsieve to 4.0.1 in src/fetch/uv.lock (3 advisories)

2 participants