Closed
Labels
choreMaintenance: deps, build tooling, CI, cleanup — no user-facing behavior changeMaintenance: deps, build tooling, CI, cleanup — no user-facing behavior changeserver-fetchReference implementation for the Fetch MCP server - src/fetchReference implementation for the Fetch MCP server - src/fetchserver-gitReference implementation for the Git MCP server - src/gitReference implementation for the Git MCP server - src/gitserver-timeReference implementation for the Time MCP server - src/timeReference implementation for the Time MCP server - src/timev2
Milestone
Description
Split out of the monthly dependency refresh (#5417).
uv lock --upgrade moves ruff from 0.8.x to 0.17.3 in all three Python servers (the declared range is ruff>=0.7.3 / >=0.8.1). That release enables rules that 0.8 did not, and ruff check . then fails on code that passes today:
| Server | Findings | Examples |
|---|---|---|
fetch |
13 | UP035/UP006 (typing.Tuple), UP007, I001, ASYNC230, SIM117, ISC004, B009, UP012 |
git |
23 (+1 ruff format change) |
UP045 (Optional[X]), I001, LOG009 (logging.WARN), SIM117, PLW1510, ISC004, PLR0402 |
time |
9 | I001, RUF010, ASYNC230, SIM117, PLW1510, B017 |
The #5417 PR keeps each lockfile's ruff at its current 0.8.x so the refresh stays a lockfile change.
Expected: each Python server locks the current ruff, ruff check . and ruff format --check . pass (fix the findings, or choose rules deliberately in [tool.ruff] where a rule is unwanted), and the ruff floor in each pyproject.toml is raised so the three servers agree. No behavior change.
Metadata
Metadata
Assignees
Labels
choreMaintenance: deps, build tooling, CI, cleanup — no user-facing behavior changeMaintenance: deps, build tooling, CI, cleanup — no user-facing behavior changeserver-fetchReference implementation for the Fetch MCP server - src/fetchReference implementation for the Fetch MCP server - src/fetchserver-gitReference implementation for the Git MCP server - src/gitReference implementation for the Git MCP server - src/gitserver-timeReference implementation for the Time MCP server - src/timeReference implementation for the Time MCP server - src/timev2
Activity
YUYU20061107 commentedon Nov 5, 2026
Hi! I'd like to work on this. Plan: bump ruff to 0.17.x in the fetch, git, and time servers, clear the new findings (fixing in code where sensible, adjusting
[tool.ruff]only where a rule clearly doesn't fit), raise the ruff floor in eachpyproject.tomlso all three agree, and confirmruff check .andruff format --check .pass with no behavior change. I'm a student and an active MCP server developer. I'll open a PR within the next few days and am happy to adjust based on feedback.YUYU20061107 commentedon Nov 5, 2026
Update: I see this was closed as completed shortly after my claim — no problem at all. For the record, I had prepared the change locally and verified it end-to-end (ruff check findings 13/23/9 → 0/0/0 across fetch/git/time, format check clean, pyright 0 errors; tests: fetch 437, git 301, time 171 passed). Per CONTRIBUTING I won't open a PR; if the prompt and approach I used would be useful for the v2 line, I'm happy to share them here.
chore(python): adopt ruff 0.17 and clear its new lint findings
chore(python): adopt ruff 0.17 and clear its new lint findings