ci: stop dependabot re-proposing the uninstallable mcp 2.x bump - #24
Merged
Conversation
Every weekly python-deps batch has carried mcp==2.0.0, and every one is uninstallable: strands-agents, claude-agent-sdk and langchain-mcp-adapters all still declare mcp<2.0.0 (pip: ResolutionImpossible). Worse, the single bad pin drags the whole grouped batch down with it — that is how a 25-package PR became unmergeable and had to be split by hand into #21-#23. Holds mcp at 1.x via an ignore rule for major updates only (minor/patch still flow). The comment says why, and names the one-line check for deciding when to remove it, so this reads as a deliberate hold rather than neglect. Also corrects the file header: it claimed GitLab is the source of truth and that bumps arrive here by export, which stopped being true when this repo became primary. The point that survives is the one that matters — CI here runs no container builds or agent invokes, so a green check on a dependency PR means little, and grouped batches should be split by risk. Verified: yaml parses, 3 update blocks, the ignore rule reads back as expected.
|
Commit: Security Scan Results
|
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
1 participant
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.
What
Every weekly
python-depsbatch carriesmcp==2.0.0, and every one is uninstallable —strands-agents,claude-agent-sdkandlangchain-mcp-adaptersall still declaremcp<2.0.0:Because the batch is grouped, that one bad pin takes 24 good bumps down with it — which is exactly how #19/#20 became unmergeable and had to be split by hand into #21–#23.
Changes
mcpat 1.x viaignoreon major updates only (minor and patch still flow). The comment explains the reasoning and names the one-line check for deciding when to lift it, so it reads as a deliberate hold rather than a forgotten pin.Verified
YAML parses, 3 update blocks intact, ignore rule reads back as expected.
Follow-up
#20 can be closed — it was generated against the pre-#21/#22/#23 base, so it re-reverts everything just merged and still carries the bad mcp pin. With this in place, the next scheduled batch should be small and mergeable.