feat(keycardai-mcp-fastmcp): release deprecation bridge for keycardai-fastmcp#103
Merged
Merged
Conversation
…-fastmcp Empty commit to trigger the auto-bump pipeline for keycardai-mcp-fastmcp. The actual bridge code (depends on keycardai-fastmcp, re-exports every public symbol at the original keycardai.mcp.integrations.fastmcp.* paths, emits DeprecationWarning on top-level import) shipped in #102. That PR landed scoped (keycardai-fastmcp), so cz only bumped the new package and keycardai-mcp-fastmcp on PyPI is still the pre-rename version. This commit gives cz a (keycardai-mcp-fastmcp)-scoped feat to recognize so the bridge ships as the next published version and customers on the old name see the deprecation warning.
📦 Release PreviewThis analysis shows the expected release impact: 📈 Expected Version Changes📋 Package Details[
{
"package_name": "keycardai-mcp-fastmcp",
"package_dir": "packages/mcp-fastmcp",
"has_changes": true,
"current_version": "0.20.0",
"next_version": "0.21.0",
"increment": "MINOR"
}
]📝 Changelog PreviewThis comment was automatically generated by the release preview workflow. |
kamil-keycard
approved these changes
Apr 27, 2026
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
2 participants
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.
Summary
Empty trigger commit to bump and publish
keycardai-mcp-fastmcpas a deprecation bridge.#102 (ACC-233) landed the bridge code under a
feat(keycardai-fastmcp): ...commit, so the auto-bump pipeline only releasedkeycardai-fastmcp. The bridge source onmainnow depends onkeycardai-fastmcpand re-exports the public API with aDeprecationWarning, but the publishedkeycardai-mcp-fastmcpon PyPI is still the pre-rename version. Customers onpip install keycardai-mcp-fastmcpwill not see the deprecation warning until the bridge version ships.This commit is empty by design. Its only job is to give cz a
(keycardai-mcp-fastmcp)-scopedfeatto recognize sobump-package.ymlproduces a new tag andrelease.ymlpublishes the bridge.Test plan
keycardai-mcp-fastmcp4-test bridge contract suite (introduced in feat(keycardai-fastmcp): rename keycardai-mcp-fastmcp via bridge package (ACC-233) #102) is unaffectedbump-package.ymlproduces a new*-keycardai-mcp-fastmcptag anduv publishsucceeds against the existing PyPI Trusted Publisherpip install keycardai-mcp-fastmcppulls the new version,import keycardai.mcp.integrations.fastmcpemits theDeprecationWarning