microshift-release:release-versions

Determine MicroShift release availability and generate a structured Markdown report.

7|15|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/openshift-eng/edge-tooling --skill microshift-release-release-versions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: microshift-release:release-versions
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/microshift-release/skills/release-versions
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill microshift-release-release-versions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MicroShift release engineers and platform users need to quickly determine whether a specific MicroShift version is available and find the correct RPM and bootc image locations without manually checking multiple catalogs and mirrors.

Core Features & Use Cases

  • Version availability & type classification: Detects whether a version is nightly, EC, RC, GA, or z-stream and whether it is available.
  • RPM package URL discovery: Produces architecture-specific mirror URLs for x86_64 and aarch64 RPM repositories appropriate to the version type.
  • Bootc image pull-spec retrieval (4.18+): Fetches bootc image pull specs via the correct mirror location when applicable.
  • OCP payload gating awareness: Checks whether the corresponding OpenShift payload is Accepted before proceeding, aligning MicroShift package creation timing with OCP status.
  • Brew build lookup (VPN required): Retrieves build status or indicates when internal Brew access is needed.

Quick Start

Ask: /microshift-release:release-versions 4.21.0-rc.1 to get a release availability report with RPM URLs and any available bootc image information.

Frequently Asked Questions about microshift-release:release-versions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a MicroShift version is available and find its RPM repository URLs?

Check MicroShift version availability by parsing the version identifier and performing mirror lookups via WebFetch. This generates a structured Markdown report classifying the release type and providing architecture-specific x86_64 and aarch64 RPM repository URLs.

What MicroShift release types can be classified and validated for build status?

MicroShift release types classified include nightly, EC, RC, GA, and z-stream versions. Validation checks OCP payload Accepted status before proceeding and queries Brew for build status, requiring VPN access for internal Brew lookups.

Can I retrieve bootc image pull specs for MicroShift versions 4.18 and later?

Yes, bootc image pull specs are retrieved for MicroShift versions 4.18 and later. The tool fetches these specs via the correct mirror location when applicable and includes them in the structured availability report.

Does MicroShift release validation require OpenShift payload acceptance before checking RPM and bootc locations?

MicroShift release validation checks whether the corresponding OpenShift payload is Accepted before proceeding. This aligns MicroShift package creation timing with OCP status to ensure release availability and correct mirror or catalog lookups.

Why do I need a VPN to check MicroShift Brew build status during release validation?

A VPN is needed to check MicroShift Brew build status because Brew is an internal build system. The validation tool retrieves build status when internal access is available and indicates when VPN is required for the lookup.

What is the best way to normalize MicroShift version identifiers for release planning?

Normalize MicroShift version identifiers by parsing the provided version string to classify it as nightly, EC, RC, GA, or z-stream. This normalization determines the correct mirror locations for RPM repositories and bootc pull specs.