Repository navigation
chore(deps): tier 1 cascade — consume tier 0 (incl. Tharga.Mcp 1.1.0 / MCP SDK 2.2.0) + externals - #18
Merged
Conversation
….14.13) and bump externals
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Released as v1.0.1 — https://github.com/Tharga/Communication/releases/tag/1.0.1 |
This branch had an error being deployed
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.
First repo of Tier 1 in the cascade update. Tier 0 is released and indexed, so this consumes it.
Internal — consuming tier 0
Tharga.Runtime1.0.0 → 1.0.1Tharga.Mcp1.0.0 → 1.1.0 (inTharga.Communication.Mcp)Tharga.Test.Toolkit1.14.12 → 1.14.13 (test project)All three verified live on nuget.org before being referenced.
The Tharga.Mcp jump is worth a second look
This is a two-version move, and 1.1.0 is the release that carries the MCP SDK
ModelContextProtocol2.0.0 → 2.2.0 upgrade. SoTharga.Communication.Mcpis adopting an SDK protocol change here, not just a patch — that is exactly why Mcp shipped it as a minor rather than a patch this time.Result: build clean at 0 warnings, and 120/120 tests pass. No API or behaviour change surfaced on this side.
External
Library
Microsoft.AspNetCore.SignalR.Client10.0.10 → 10.0.11Microsoft.AspNetCore.SignalR.Client.Core10.0.10 → 10.0.11Microsoft.SourceLink.GitHub10.0.301 → 10.0.400 (both library projects;PrivateAssets=all, build-only)Test tooling (does not ship)
Microsoft.AspNetCore.Mvc.Testing10.0.10 → 10.0.11Microsoft.Extensions.Hosting10.0.10 → 10.0.11Microsoft.NET.Test.Sdk18.6.0 → 18.9.0Moq.AutoMock4.0.2 → 4.0.3Verification
dotnet build -c Release— clean, 0 warnings.dotnet test -c Release— 120/120 passing.No source changes, no public API change, no
MAJOR_MINORbump.Note on what this release also ships:
mastercarried two unreleased commits — thesnupkgsymbol-publishing fix from #17 — so releasing this publishes that too.Process note: a deliberate dependency-only PR rather than one bundled into a feature, because the change has to cross all fifteen repos in tier order.