imatza-rh/mcp-zuul

v0.5.1 Breaking

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

Published 2mo MCP Developer Tools

✓ No known CVEs patched

✓ No known CVEs patched in this version

Summary

AI summary

Connection error messages now classify the underlying cause and get_build_log clamps negative lines parameter to valid range.

Full changelog

fmt_build computes human-readable elapsed field for IN_PROGRESS builds in non-brief mode, eliminating manual UTC arithmetic when monitoring running builds via get_change_status
Connection error messages now classify the underlying cause (DNS resolution failed, connection refused, network unreachable) instead of generic "Cannot connect to Zuul API"

get_build_log with negative lines parameter no longer produces empty/wrong output - values are clamped to valid range
File-level corrupted gzip in log tools now shows the same helpful "use diagnose_build" message as HTTP-level gzip errors
Removed dead exception types (gzip.BadGzipFile, zlib.error, EOFError, OSError) from _fetch_job_output catch block - these are now handled inside _decompress_gzip

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.