Repository navigation
release: v0.17.0 - #32
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Release v0.17.0 — first minor bump since v0.16.0 (2026-05-22).
What's new
🆕
maestro_subscription_outcomesMCP tool (#31)Lists categorized subscription trigger outcomes from the new PCS
ISubscriptionTriggerOutcomesAPI. Filterable by subscription, build, date range, and outcome type. Single-line, LLM-friendly output with emoji prefixes:🩺
maestro_subscription_healthsurfacesLatestOutcome(#31)For each stale subscription, the most recent trigger outcome (type + message) is rendered inline. Ground-truth diagnostic data from PCS replaces guesswork for why a subscription is stuck. Existing heuristics (oscillation, TrackedPrDiagnosis, GitHub compare) retained as a complement; a TODO flags them for future retirement once outcomes data is trusted across more sessions.
🔐 Security hardening
Microsoft.Data.Sqlitestill pulls SQLitePCLRaw 2.1.x transitively; we pin to 3.x where the fix shipped.Mcp-Session-Id). Both apply to this server.🛠 Infra
Dependency bumps
Microsoft.DotNet.ProductConstructionService.ClientModelContextProtocol/.AspNetCoreMicrosoft.Extensions.DependencyInjectionSQLitePCLRaw.bundle_e_sqlite3/.core/.provider.e_sqlite3SQLitePCLRaw.lib.e_sqlite3After merge
Tag
v0.17.0and push —publish.ymlwill pack and push to NuGet via OIDC trusted publishing.