Repository navigation
chore(fetch): raise the Python floor to 3.11.5 so the lock drops soupsieve 2.10 - #5567
Conversation
…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>
|
|
| Tools | Prompts | Resources | Resource templates | |
|---|---|---|---|---|
| Base | 1 | 1 | 0 | 0 |
| Head | 1 | 1 | 0 | 0 |
Updated by this run for 31a72754c3b6048624929fad517a6261479af152.
There was a problem hiding this comment.
🟢 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
|
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. |
Closes #5546
Description
Raises
mcp-server-fetch's Python floor from>=3.10to>=3.11.5and re-locks, sosrc/fetch/uv.lockno longer holds asoupsieveinside any of the three advisory ranges on #5546.This is a floor bump for the published
mcp-server-fetchpackage (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
soupsieverelease patched against these advisories (3.0.2 and up, including 4.0.0) declaresrequires-python >=3.11.5. With fetch at>=3.10, uv forked the lock:4.0.1for>= 3.11.5and the vulnerable2.10for everything older.uv lock --upgrade-package soupsievecannot 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"; the3.10classifier becomes3.11(git and time list their floor's minor the same way).src/fetch/uv.lock: re-locked withuv lock. No package version is added or bumped. Twelve entries are removed, all of them the old floor's: thesoupsieve 2.10fork, 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
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 throughbeautifulsoup4.How Has This Been Tested?
No client-observable surface changes, so these are targeted probes:
grep -A1 'name = "soupsieve"' src/fetch/uv.lockgives a single entry,4.0.1(ranges on the issue:<= 2.10,>= 0.4, <= 2.10,< 4.0.0).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).uv run --frozen --python 3.11.5 pytestinsrc/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 checkandruff format --check: clean.uv sync --locked --python 3.10fails with "incompatible with the project's Python requirement:>=3.11.5".(name, version)set of the lock before and after gives 12 removed, 0 added.npm run local:gateexits 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-fetchon Python 3.10 through 3.11.4: they need Python 3.11.5 or newer.uvxusers are unaffected (uv fetches a suitable interpreter), as are Docker users (the image is on 3.12). No client configuration changes.Types of changes
Checklist
🤖 Generated with Claude Code