chore(deps): say why mcp<2 and pyiceberg-core<0.8 are load-bearing

Dependabot has re-proposed both ceilings since 2026-08-23 (#244, #245) and
both PRs sat unmergeable for sixteen days. Each pin had a one-line reason
in a comment; neither reason was checkable without doing the work, so
nobody did, and the PRs stayed open. Checked now, recorded where the pin
is, and taught Dependabot to stop asking.

mcp<2 holds. mcp 2.2.0 still exports Server from mcp.server, but its
lowlevel Server defines neither list_tools nor call_tool, and
integrations/agentflow_integrations/mcp/server.py is built entirely out of
@server.list_tools() and @server.call_tool(). #244 proposed <3; taking
mcp 2 is a port of that module, not a range change. Both halves of the
mirrored pin now say which decorators are missing and which file needs
the port.

pyiceberg-core<0.8 holds, for a reason the old comment only half stated.
PyIceberg 0.11.1 declares pyiceberg-core>=0.5.1,<0.9.0, so 0.8.0 is the
only step up inside the pairing upstream supports -- and 0.8.0 is the one
release in the line published as requires-python <3.13, which the
3.11-3.13 `environments` in [tool.uv] rule out. 0.9.0/0.9.1 restored 3.13
but sit outside PyIceberg's window. So nothing above 0.7 is installable
here, which #245's <0.11 does not change: widening alone leaves the lock
on 0.7.0 (verified -- `uv lock` rewrites only the recorded specifier),
and `uv lock --upgrade-package pyiceberg-core` under it jumps to 0.10.1,
i.e. exactly the pairing PyIceberg says it does not support. The ceiling
moves when PyIceberg raises its own, and that arrives as a pyiceberg PR.

.github/dependabot.yml ignores mcp majors -- in the root and integrations
ecosystems, since they own the two halves of the same pin -- and
pyiceberg-core minors, each with the reason and the exit condition inline.
The file's existing NOTE about `ignore` also suppressing security updates
applies unchanged: safety and pip-audit scan both packages and fail on a
CVE that only a blocked bump would fix.

No resolution change: `uv lock --check` passes untouched (256 packages).
test_security_tooling_policy.py, test_contract_dependencies.py,
test_cross_package_install_contract.py and test_mcp_server.py pass (44
passed), scripts/validate_project_claims.py OK, docs ratchets pass (33
passed).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018ybRVCaL1Lyd9d5kFTndh3

Author: JuliaEdom

.github/dependabot.yml

@@ -64,6 +64,23 @@ updates:
         update-types: ["version-update:semver-major"]
       - dependency-name: "dagster"
         update-types: ["version-update:semver-major"]
+      # mcp 2.x's lowlevel Server drops the list_tools/call_tool decorators
+      # integrations/agentflow_integrations/mcp/server.py is built on (checked
+      # against 2.2.0), so a major bump is a port, not an update. PR #244
+      # proposed <3 and was closed on that basis; the ignore stops it coming
+      # back weekly. Same NOTE above applies: the safety/pip-audit jobs still
+      # scan mcp and fail on a CVE that only a major fixes.
+      - dependency-name: "mcp"
+        update-types: ["version-update:semver-major"]
+      # pyiceberg-core is pinned to the release PyIceberg pairs with, not to
+      # the newest one. PyIceberg 0.11.1 declares pyiceberg-core>=0.5.1,<0.9.0;
+      # the only step up inside that window is 0.8.0, published as
+      # requires-python <3.13, which the 3.11-3.13 resolution environments in
+      # pyproject.toml rule out. Bumps only make sense when PyIceberg raises
+      # its own range, and that arrives as a pyiceberg PR. PR #245 proposed
+      # <0.11 and was closed on that basis.
+      - dependency-name: "pyiceberg-core"
+        update-types: ["version-update:semver-minor"]
 
   # ── Python: Flink runtime image manifest ───────────────────────────
   # Not an extra of the root project (its beam chain can never co-install
@@ -120,6 +137,12 @@ updates:
       - dependencies
       - python
       - integrations
+    ignore:
+      # The other half of the mirrored mcp pin (see the root pip entry): the
+      # ceiling is what the integration's decorators need, so leaving this
+      # ecosystem unignored just reopens the same PR from the other directory.
+      - dependency-name: "mcp"
+        update-types: ["version-update:semver-major"]
 
   # ── npm: TypeScript SDK ────────────────────────────────────────────
   - package-ecosystem: npm

CHANGELOG.md

@@ -4,6 +4,28 @@ All notable changes to AgentFlow are documented in this file.
 
 ## [Unreleased]
 
+### Dependencies — the two version ceilings that keep coming back are now explained
+
+* **`mcp<2` is load-bearing.** mcp 2.x's lowlevel `Server` no longer defines
+  `list_tools` or `call_tool` (checked against 2.2.0), and
+  `integrations/agentflow_integrations/mcp/server.py` builds its whole surface
+  out of `@server.list_tools()` and `@server.call_tool()`. Taking mcp 2 means
+  porting that module first. Both halves of the mirrored pin
+  (`pyproject.toml` and `integrations/pyproject.toml`) now say so.
+* **`pyiceberg-core<0.8` is not a stale ceiling.** PyIceberg 0.11.1 declares
+  `pyiceberg-core>=0.5.1,<0.9.0`, so 0.8.0 is the only step up inside the
+  pairing upstream supports — and 0.8.0 is the one release in the line
+  published as `requires-python <3.13`, which the 3.11–3.13 resolution
+  `environments` rule out. 0.9+ restored 3.13 but sits outside PyIceberg's
+  declared window. Nothing in that window is installable, so the ceiling
+  moves when PyIceberg raises its own.
+* **Dependabot stops re-proposing both.** `.github/dependabot.yml` ignores
+  `mcp` majors (in the root *and* integrations ecosystems, which own the two
+  halves of the same pin) and `pyiceberg-core` minors, each with the reason
+  and the exit condition. The existing NOTE about `ignore` also suppressing
+  security updates still applies: `safety` and `pip-audit` scan both
+  packages and fail on a CVE that only a blocked bump would fix.
+
 ### Quality — the key-rotation coverage gate was passing on a rounding margin
 
 * **89.6% rounds to 90.** The gate on `serving/api/auth/key_rotation.py` ran

integrations/pyproject.toml

@@ -26,7 +26,9 @@ dependencies = [
 
 [project.optional-dependencies]
 mcp = [
-    # MCP 2 removes the low-level Server decorators used by this integration.
+    # mcp 2.x's lowlevel Server drops the list_tools/call_tool decorators
+    # server.py is built on (checked against 2.2.0). Port the module before
+    # moving this pin; the root pyproject mirrors it.
     "mcp>=1.0,<2",
 ]
 

pyproject.toml

@@ -40,8 +40,14 @@ dependencies = [
 cloud = [
     "boto3>=1.35,<2",
     "pyiceberg>=0.7,<1",
-    # PyIceberg 0.11 write paths require native transforms. Core 0.8 excludes
-    # Python 3.13, while 0.7 provides a stable-ABI wheel across Python 3.11-3.13.
+    # PyIceberg 0.11 write paths require native transforms, and 0.7 is the
+    # only core release that can serve them here. PyIceberg 0.11.1 declares
+    # pyiceberg-core>=0.5.1,<0.9.0, so 0.8.0 is the only step up inside the
+    # pairing upstream supports -- and 0.8.0 is the one release in the line
+    # published as requires-python <3.13, which the 3.11-3.13 resolution
+    # environments below rule out. (0.9+ restored 3.13 but sits outside
+    # PyIceberg's declared window; nothing in that window is installable.)
+    # The ceiling moves when PyIceberg raises its own, not before.
     "pyiceberg-core>=0.7,<0.8",
 ]
 postgres = [
@@ -77,8 +83,11 @@ integrations = [
     "llama-index-core>=0.12,<1",
     # Mirrors integrations/pyproject.toml [mcp]: locking it here lets CI
     # install the editable integrations package with --no-deps from the
-    # frozen root resolution (audit F-05). MCP 2 removes the low-level
-    # Server decorators the integration uses.
+    # frozen root resolution (audit F-05). The ceiling is load-bearing:
+    # mcp 2.x's lowlevel Server no longer defines list_tools or call_tool
+    # (checked against 2.2.0), and integrations/.../mcp/server.py builds its
+    # whole surface out of @server.list_tools() and @server.call_tool().
+    # Taking mcp 2 means porting that module first, not moving this pin.
     "mcp>=1.0,<2",
 ]
 contract = [