Release Notes Action Items for mcpg 0.3.12 → 0.3.21
This issue summarizes upstream release notes for the mcpg dependency between the previously pinned version (0.3.12) and the new pinned version (0.3.21), highlighting items that may need follow-up in ado-aw.
The companion version-bump PR is titled chore(deps): update MCPG_VERSION to 0.3.21.
Releases analyzed
Notable features for ado-aw to adopt
- Standardize gateway JSONL records with
event/_schema and millisecond timestamps — v0.3.19: MCPG now uses standardized JSONL event format. If ado-aw consumes or produces MCPG-compatible JSONL, it should align with this format for consistency.
- Close GitHub guard DIFC gaps for
search_commits and FF list_issues variant — v0.3.19: MCPG now enforces DIFC labeling for additional tools. Ado-aw should review whether similar gaps exist in its own DIFC implementation.
- Enforce per-session tool call limits in allow-only guard policies — v0.3.20: MCPG now enforces per-session tool call limits. Ado-aw may want to adopt similar rate-limiting to prevent agent runaway or resource exhaustion.
- Fix DIFC proxy handling for top-level array responses on comment list endpoints — v0.3.20: MCPG fixed a DIFC bug where top-level array responses weren't properly labeled. If ado-aw implements similar DIFC proxy logic for ADO APIs, it should ensure array responses are handled correctly.
- Improve OTel trace signal quality: stack traces, route cardinality, rate-limit status, and container resource metadata — v0.3.21: MCPG enhanced OpenTelemetry tracing with better span attributes. Ado-aw could adopt these observability improvements for its own agent-stats or OTel integration.
- Add explicit DIFC labeling for
list_issue_fields in GitHub guard — v0.3.21: MCPG added DIFC labeling for a new GitHub MCP tool method. If ado-aw adds similar ADO tools, it should ensure DIFC labels are assigned.
- Fix tracing: semconv v1.27.0→v1.34.0, fix mcp.tool_call attribute misuse, add server.address — v0.3.21: MCPG upgraded to OpenTelemetry semantic conventions v1.34.0. Ado-aw should align its OTel usage with the latest conventions for consistency.
- WASM guard robustness improvements — v0.3.18: MCPG hardened its WASM guard runtime with oversized response handling, larger I/O buffers, and improved cache locking. If ado-aw uses WASM guards, it should consider similar robustness improvements.
This issue was opened automatically by the dependency version updater workflow.
Generated by Dependency Version Updater · ● 5.1M · ◷
Release Notes Action Items for
mcpg0.3.12→0.3.21This issue summarizes upstream release notes for the
mcpgdependency between the previously pinned version (0.3.12) and the new pinned version (0.3.21), highlighting items that may need follow-up in ado-aw.The companion version-bump PR is titled
chore(deps): update MCPG_VERSION to 0.3.21.Releases analyzed
Notable features for ado-aw to adopt
event/_schemaand millisecond timestamps — v0.3.19: MCPG now uses standardized JSONL event format. If ado-aw consumes or produces MCPG-compatible JSONL, it should align with this format for consistency.search_commitsand FFlist_issuesvariant — v0.3.19: MCPG now enforces DIFC labeling for additional tools. Ado-aw should review whether similar gaps exist in its own DIFC implementation.list_issue_fieldsin GitHub guard — v0.3.21: MCPG added DIFC labeling for a new GitHub MCP tool method. If ado-aw adds similar ADO tools, it should ensure DIFC labels are assigned.This issue was opened automatically by the dependency version updater workflow.