microshift-release:pre-check

You can evaluate MicroShift release readiness by running a pre-check that queries the OCP schedule, lifecycle state, payload availability, advisory CVEs, and Brew RPM presence to output an explicit action like OK, SKIP, or NEEDS REVIEW.

The best way to verify MicroShift participation in nightly or EC releases is to run a pre-check that evaluates nightly gaps, EC/RC readiness, and payload availability, yielding a clear decision such as OK, SKIP, or ASK ART.

Yes, you can find OCP z-stream versions scheduled within a specific window using natural-language time-range lookups, provided the optional Product Pages MCP is configured for the query.

Brew checks require VPN access, and advisory CVE checks require tokens, but the pre-check supports graceful degradation, continuing the evaluation with available data when these optional prerequisites are missing.

When Product Pages MCP is missing, time-range schedule lookups are unavailable, and without VPN or tokens, Brew and CVE advisory checks degrade gracefully, limiting the pre-check to version-specific availability and lifecycle status evaluations.