imatza-rh/mcp-zuul

v0.3.1 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 2mo MCP Developer Tools

✓ No known CVEs patched

✓ No known CVEs patched in this version

Affected surfaces

breaking_upgrade

Summary

AI summary

get_build_failures API renames two fields, breaking existing callers.

Full changelog

diagnose_build — One-call failure diagnosis combining structured failures from job-output.json with targeted log context (fatal:/FAILED! lines with 5-line surrounding context from job-output.txt). Use instead of calling get_build_failures + get_build_log separately.

Grep context deduplication — Adjacent matches with overlapping context ranges are now merged into single blocks instead of producing redundant output in get_build_log.
Richer failure output — get_build_failures now includes all playbook summaries (not just failed ones) with a failed flag, showing full pipeline progression in one call.
Increased truncation limits — stdout/stderr truncation increased from 1000 to 4000 chars for better visibility into nested playbook errors.
Compact passing playbooks — Passing playbooks emit only phase/name/failed (no stats or full path), reducing response size by ~69% on the playbook section (~400 tokens saved per call).

get_build_failures field renames: failed_playbooks → playbooks, total_playbooks → playbook_count.

Full Changelog: https://github.com/imatza-rh/mcp-zuul/compare/v0.3.0...v0.3.1

`get_build_failures` renames: `failed_playbooks` → `playbooks`, `total_playbooks` → `playbook_count`

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track imatza-rh/mcp-zuul

Get notified when new releases ship.

About imatza-rh/mcp-zuul

Zuul CI integration with 14 tools for build failure analysis, log search, pipeline status, and job configuration.