Repository navigation
chore: release 0.7.1 - #7
Merged
Merged
Conversation
Changelog entry for the mcp/sdk ^0.7.1 bump already on main. Cutting the tag is what lets a consumer install all four DPT warm servers on one SDK version -- without it, dpt/mcp-phpunit-warm v0.4.1 cannot be installed alongside this one. Co-Authored-By: Max <noreply>
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.
Changelog entry for the
mcp/sdk ^0.7.1bump already merged in #6. No code change.Why now
dpt/mcp-phpunit-warmv0.4.1 (the #3 stdout-leak fix) requiresmcp/sdk ^0.7.1. A consumer that installs several DPT warm servers resolves one SDK for all of them, so until this repo,mcp-rector-warmandmcp-phpmd-warmpublish releases carrying the same requirement, composer refuses the upgrade:Tagging
v0.7.1is what unblocks that.^0.7consumers pick it up with no constraint change on their side.