Repository navigation
fix(deps): require the patched mcp and python-dotenv releases - #265
Merged
Merged
Conversation
Moves the locked versions of vulnerable Python and mock-server packages to patched releases inside the ranges pyproject.toml already allows. The mock server's exact @modelcontextprotocol/sdk pin moves from 1.24.3 to 1.32.1. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Guillaume Lebedel <10488548+glebedel@users.noreply.github.com>
Relocks from main with exact versions (the highest first-patched version of each alerted package), so nothing moves further than the advisories require and every new release is at least 14 days old, in line with the 7-day minimumReleaseAge the mock server already enforces. Moves body-parser in the mock server to 2.4.0 for GHSA-27r3-jxmh-p828. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Guillaume Lebedel <10488548+glebedel@users.noreply.github.com>
…s through langgraph-sdk 0.4.6 is the first patched version and resolves with langgraph 1.2.14, so the lock goes no further. The mock server's MCP SDK ignore now blocks majors only, as its comment says: 1.32.1 still serves the raw inputSchema, and ignoring every version also hid future security updates. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Guillaume Lebedel <10488548+glebedel@users.noreply.github.com>
uv.lock is not part of the published package, so the lockfile bumps only protect this repo. With the floors at mcp>=1.24.3 and python-dotenv>=1.0.1, an environment that already has mcp 1.25 keeps it when stackone-ai is installed. The floors now start at the first release that fixes every open advisory (mcp 1.30.0, python-dotenv 1.2.2), so the resolver upgrades instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Guillaume Lebedel <10488548+glebedel@users.noreply.github.com>
pydantic published four medium advisories (GHSA-955g-x97g-8mcp, GHSA-gj4f-r7mf-jjxh, GHSA-3r8g-cqwr-jr29, GHSA-qpmf-fgh3-ff25) that affect the locked 2.12.5 and are fixed in 2.14.2. They are not in the global advisory database yet, so Dependabot has not raised them. cohere moves to 7.2.0, the oldest release that accepts the new pydantic-core; typing-inspection stays on 0.4.4 to respect the 7-day release age. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Guillaume Lebedel <10488548+glebedel@users.noreply.github.com>
…nto s2d2/audit-raise-dependency-floors
Conflicts in package.json, pnpm-lock.yaml and uv.lock after main took the hono 4.13.16 bump and the grouped Python updates. package.json keeps this branch's MCP SDK 1.32.1 and main's hono 4.13.16. uv.lock starts from main and re-applies this branch's security bumps, so no package is lower than on either side. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Guillaume Lebedel <10488548+glebedel@users.noreply.github.com>
…lockfiles branch That branch already carries main and the lockfile conflict resolution, so this merge applies cleanly. The raised mcp and python-dotenv floors sit on top of it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Guillaume Lebedel <10488548+glebedel@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Raises two dependency floors so people who install
stackone-aiget the security fixes, not only this repo.uv.lockis not part of the published package, so #264's lockfile bumps protect CI and contributors but not users: withmcp>=1.24.3, an environment that already has mcp 1.25 keeps it, along with its open advisories.Builds on #264. Merge #264 first; this PR's own change is the last commit, 2 lines in
pyproject.tomland the 2 matchingrequires-distlines inuv.lock.mcp(core)>=1.24.3,<2.0.0>=1.30.0,<2.0.0python-dotenv(examples extra)>=1.0.1>=1.2.2How it was verified
The built wheel now declares
Requires-Dist: mcp<2.0.0,>=1.30.0andRequires-Dist: python-dotenv>=1.2.2; extra == 'examples'. Resolving the wheel next to an environment pinned tomcp==1.25.0:uv sync --locked --all-extras(Python 3.13),uv lock --checkruff check,ruff format --check,ty check stackone_ai examplesuv run pytestThe cost for consumers: anyone pinned to an older mcp gets a resolver conflict and has to upgrade, which is the point.
Not in this PR, left for a separate decision because they constrain what users' own apps can install: the adapter floors
langchain-core>=0.3.36andpydantic-ai-slim>=1.83.0admit releases with published advisories, andpydantic>=2.10.6admits releases affected by pydantic's four medium advisories (this repo's lock is on the fixed 2.14.2 since #251). Themcp<2.0.0cap stays: the 2.x move is #208.Gates
pydantic>=2.11.0to mirror mcp's own requirement (the resolver already enforces it through mcp, and a copy is a second place to keep in sync); lifting the<2.0.0cap (out of scope, #208)Requested by guillaume@stackone.com in Slack (repo audit thread).
🤖 Generated with Claude Code