Release Notes Action Items for mcpg 0.3.12 → 0.3.18
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.18), 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.18.
Releases analyzed
Notable features for ado-aw to adopt
- Sentry OTLP export support and
sentry.io network allowlist (v0.3.13): mcpg added Sentry OTLP telemetry export and a corresponding sentry.io network allowlist entry. ado-aw maintains its own network allowlist (src/data/ecosystem_domains.json and src/allowed_hosts.rs); if mcpg's Sentry OTLP export is used in production pipelines, ado-aw may need to expose sentry.io as an allowed host for consumers wishing to capture mcpg traces.
OTEL_EXPORTER_OTLP_HEADERS env var fallback for OTLP export headers (v0.3.13): mcpg now reads this standard env var as a fallback. If ado-aw passes environment variables through to mcpg, consumers can configure OTLP export via this env var without modifying mcpg config.- OTLP endpoint path fixed to append
/v1/traces per spec (v0.3.15): fix(tracing): append /v1/traces to OTLP endpoint per spec. Consumers relying on ado-aw-generated pipelines with OTLP tracing should verify their endpoint configuration after this fix.
- gen_ai semantic conventions alignment for OTel span attributes (v0.3.16):
feat(tracing): align span attributes with gen_ai semantic conventions. Consumers relying on specific OTel attribute names from mcpg (e.g. for dashboards or alerting) should verify compatibility with this attribute rename.
- WASM guard hardening: oversized
call_backend responses handled via size-hint protocol (v0.3.18): The wazero-based guard runtime now handles large responses more reliably with larger I/O buffers and improved cache reconfiguration locking.
This issue was opened automatically by the dependency version updater workflow.
Generated by Dependency Version Updater · ● 15.4M · ◷
Release Notes Action Items for
mcpg0.3.12→0.3.18This issue summarizes upstream release notes for the
mcpgdependency between the previously pinned version (0.3.12) and the new pinned version (0.3.18), 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.18.Releases analyzed
Notable features for ado-aw to adopt
sentry.ionetwork allowlist (v0.3.13): mcpg added Sentry OTLP telemetry export and a correspondingsentry.ionetwork allowlist entry. ado-aw maintains its own network allowlist (src/data/ecosystem_domains.jsonandsrc/allowed_hosts.rs); if mcpg's Sentry OTLP export is used in production pipelines, ado-aw may need to exposesentry.ioas an allowed host for consumers wishing to capture mcpg traces.OTEL_EXPORTER_OTLP_HEADERSenv var fallback for OTLP export headers (v0.3.13): mcpg now reads this standard env var as a fallback. If ado-aw passes environment variables through to mcpg, consumers can configure OTLP export via this env var without modifying mcpg config./v1/tracesper spec (v0.3.15):fix(tracing): append /v1/traces to OTLP endpoint per spec. Consumers relying on ado-aw-generated pipelines with OTLP tracing should verify their endpoint configuration after this fix.feat(tracing): align span attributes with gen_ai semantic conventions. Consumers relying on specific OTel attribute names from mcpg (e.g. for dashboards or alerting) should verify compatibility with this attribute rename.call_backendresponses handled via size-hint protocol (v0.3.18): The wazero-based guard runtime now handles large responses more reliably with larger I/O buffers and improved cache reconfiguration locking.This issue was opened automatically by the dependency version updater workflow.