microshift-release:validate-artifacts

To validate MicroShift release artifacts, run the validation command with a target version like 4.22.0-rc.2. It checks Brew-built RPM package lists, NVR/commit provenance, bootc shipment MR metadata, and catalog publication to ensure release readiness.

RPM provenance verification confirms expected Brew packages are present, validates NVR/filename formatting, ensures the commit belongs to the correct release branch, and checks that required RHEL variants exist for the target MicroShift release.

Yes, you need a VPN for Brew and internal git provenance checks. Network mirror access is required for RC/EC mirror validations, and an optional GITLAB_API_TOKEN can be supplied for bootc shipment MR verification.

Bootc shipment checks are enforced for MicroShift versions 4.18 and above. The validation confirms shipment MR content, checks X/Y.0-specific metadata rules, verifies advisory URLs, and ensures SHA/pullspec consistency for RC/EC flows.

Yes, MicroShift artifact validation applies to RC, EC, GA (X/Y.0), Z-stream, and nightly workflows. Mirror and SHA consistency rules are specifically applied to the relevant release types during the validation process.

Mirror availability errors occur during RC/EC flows when network mirror access is unavailable. Ensure your connection allows reaching the required mirrors, as RC/EC mirror validations explicitly depend on this external network access.