From 797b4cdcfec98b1162b91087c8e7ea86e2580826 Mon Sep 17 00:00:00 2001 From: "keycard-gh-workflows-access[bot]" <259488581+keycard-gh-workflows-access[bot]@users.noreply.github.com> Date: Wed, 29 Jul 2026 00:21:18 +0000 Subject: [PATCH] =?UTF-8?q?bump:=20keycardai-mcp=20=E2=86=92=200.27.0?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Auto-bump for keycardai-mcp. --- packages/mcp/CHANGELOG.md | 19 +++++++++++++++++++ packages/mcp/pyproject.toml | 2 +- 2 files changed, 20 insertions(+), 1 deletion(-) diff --git a/packages/mcp/CHANGELOG.md b/packages/mcp/CHANGELOG.md index a452c68..c30cc31 100644 --- a/packages/mcp/CHANGELOG.md +++ b/packages/mcp/CHANGELOG.md @@ -1,3 +1,22 @@ +## 0.27.0-keycardai-mcp (2026-07-29) + + +- fix(keycardai-mcp): cap mcp below 2.0 (#219) +- mcp 2.0.0 published 2026-07-28. The floor was unbounded, so fresh +installs began resolving onto the new major immediately, against code +written for 1.x. +- Capping rather than porting because the wider ecosystem has not crossed +over. Two of the four agent frameworks this package ships integrations +for still pin mcp below 2.0 outright: +- openai-agents 0.19.0 mcp<2,>=1.19.0 + crewai 1.15.8 mcp~=1.28.1 +- fastmcp 3.x pins it too. A hard mcp>=2.0 floor here would make +keycardai-mcp uninstallable next to any of them. +- The 2.0 port itself is written and green in #218; it lands once those +pins move. +- Co-authored-by: GitHub Action +Co-authored-by: Claude Opus 5 (1M context) + ## 0.26.0-keycardai-mcp (2026-06-15) diff --git a/packages/mcp/pyproject.toml b/packages/mcp/pyproject.toml index 6a17390..14022e3 100644 --- a/packages/mcp/pyproject.toml +++ b/packages/mcp/pyproject.toml @@ -137,7 +137,7 @@ filterwarnings = [ [tool.commitizen] name = "cz_customize" -version = "0.26.0" +version = "0.27.0" tag_format = "${version}-keycardai-mcp" ignored_tag_formats = ["${version}-*"] update_changelog_on_bump = true