Skip to content

fix(deps): bump mcp to 2.3.0 and allow pillow 13 - #1174

Merged
robert-ursu merged 4 commits into
mainfrom
fix/bump-mcp
Oct 22, 2026
Merged

robert-ursu merged 4 commits into
mainfrom
fix/bump-mcp

Conversation

@robert-ursu

@robert-ursu robert-ursu commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Bumps the exact mcp pin from 2.0.0 to 2.3.0, and the package version to 0.18.50.

mcp 2.0.0 carries CVE-2026-59951 (MEDIUM), fixed in 2.2.0. Because the pin is exact, nothing installed alongside uipath-langchain can move past it; a constraint file in a downstream install fails to resolve instead. The lockfile changes only mcp and mcp-types (2.0.0 → 2.3.0) and this package's own version.

It also widens the pillow range to >=12.3.0, <14.0.0. pillow 12.3.0 carries CVE-2026-112403 (CRITICAL) and six HIGH CVEs in its JPEG, GIF, TIFF and PDF code, all fixed in 13.0.0, and the <13 cap kept every downstream install on 12.x. This repository's lock stays on 12.3.0, because deepagents[video] still caps pillow below 13; installs without that extra can now move to 13.

Test plan

  • tests/agent/tools/test_mcp: 136 passed, including the tests against real MCP servers over HTTP
  • Full suite locally on Windows: the only failures are 3 in test_uipath_cli_tool.py, which start the uip CLI as a subprocess, unrelated to mcp
  • With pillow 13.0.0 installed: tests/agent/multimodal 52 passed, and a two-page TIFF converts to PNG pages the way download_tiff_pages does it
  • CI

🤖 Generated with Claude Code

robert-ursu and others added 2 commits October 21, 2026 15:34
mcp 2.0.0 carries CVE-2026-59951, fixed in 2.2.0. The exact pin keeps
downstream installs from moving past it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
pillow 12.3.0 carries CVE-2026-112403 (critical) and six high CVEs in its
JPEG, GIF, TIFF and PDF code, all fixed in 13.0.0. The <13 cap kept
downstream installs on 12.x. The lock stays on 12.3.0 because
deepagents[video] still caps pillow below 13.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@robert-ursu robert-ursu changed the title fix(deps): bump mcp to 2.3.0 fix(deps): bump mcp to 2.3.0 and allow pillow 13 Oct 21, 2026
@robert-ursu
robert-ursu marked this pull request as ready for review October 22, 2026 13:11
Copilot AI balanced review requested due to automatic review settings October 22, 2026 13:11
The MCP samples and test cases pin mcp themselves, so they have to follow the
library's pin. litellm 1.89.3 has GHSA-3cv6-jpf6-8222, fixed in 1.89.7 on the
same minor line, and CI's package proxy now refuses to download 1.89.3.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟡 Changes recommended

Two editable-root integration testcases still pin MCP 2.0.0, conflicting with the SDK’s new exact requirement and preventing dependency resolution.

1 open issue
What changed in this PR

Updates the SDK’s dependencies to use MCP 2.3.0 and permit Pillow 13, addressing constraints that prevented downstream security upgrades.

Changes:

  • Bumps the package version to 0.18.50.
  • Updates MCP and MCP Types to 2.3.0 in the lockfile.
  • Widens Pillow’s upper bound to <14.0.0, while retaining locked version 12.3.0.
File Description
uv.lock Updates MCP packages, SDK version, and dependency metadata.
pyproject.toml Bumps the SDK version and adjusts MCP and Pillow requirements.

Review effort: Balanced

Comment thread pyproject.toml
"jsonpath-ng>=1.7.0",
"mcp==2.0.0",
"pillow>=12.3.0, <13.0.0",
"mcp==2.3.0",
Their mcp pin moved to 2.3.0, which only uipath-langchain 0.18.50 and later
allow, so a lower floor would resolve to an unsatisfiable set.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

@robert-ursu
robert-ursu merged commit 12876f5 into main Oct 22, 2026
47 checks passed
@robert-ursu
robert-ursu deleted the fix/bump-mcp branch October 22, 2026 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants