Skip to content

NO-ISSUE: new Claude command to get info about MicroShift versions availability#5919

Merged
openshift-merge-bot[bot] merged 5 commits intoopenshift:mainfrom
agullon:claude-command-release-versions
Dec 17, 2025
Merged

NO-ISSUE: new Claude command to get info about MicroShift versions availability#5919
openshift-merge-bot[bot] merged 5 commits intoopenshift:mainfrom
agullon:claude-command-release-versions

Conversation

@agullon
Copy link
Contributor

@agullon agullon commented Dec 16, 2025

Example:
/microshift-release-versions 4.21-RC

Output:

MicroShift Version Availability: 4.21 RC

Status

  • Version: 4.21.x-rc.x
  • Type: Release Candidate (RC)
  • Status: Not Yet Available
  • Current Phase: Engineering Candidate (EC)

Current State

MicroShift 4.21 is currently in the EC phase. No RC versions have been created yet.

Available EC Versions

The following EC versions are available:

When Will RC Versions Be Available?

RC (Release Candidate) versions are created after branch cutoff until GA. The 4.21 branch has not cut off yet, so RC versions are not expected at this time.

Timeline:

  1. Current: EC phase (4.21.0-ec.x)
  2. Next: Branch cutoff (date TBD)
  3. Then: RC phase begins (4.21.0-rc.x)
  4. Finally: GA release (4.21.0)

How to Track Progress

Monitor the OpenShift Release Status page for:

  • RC version creation
  • Acceptance status of new builds

Notes

  • RC versions will appear in the mirror repository once created
  • Until then, use the latest EC version (4.21.0-ec.3) for testing
  • GA release is expected approximately 4 months after the previous major release (4.20)

@openshift-ci-robot
Copy link

@agullon: This pull request explicitly references no jira issue.

Details

In response to this:

Example:
/microshift-release-versions 4.21-RC

Output:

MicroShift Version Availability: 4.21 RC

Status

  • Version: 4.21 RC
  • Type: Release Candidate (RC)
  • Status: Not Yet Available
  • Current Phase: Engineering Candidate (EC)

Summary

4.21 is currently in the EC phase. No RC versions have been created yet.

Available 4.21 EC Versions (Dev Preview)

Based on the search of mirror.openshift.com:

  • 4.21.0-ec.3 (Latest)
  • 4.21.0-ec.0

When Will RC Versions Be Available?

RC versions are created after branch cutoff and continue until GA. The 4.21 release is currently in active development with EC versions being published every sprint (approximately every 3 weeks).

Timeline expectations:

  1. Current Phase: EC versions (ongoing)
  2. Next Phase: RC versions (after branch cutoff)
  3. Final Phase: GA release (expected ~4 months after previous GA)

How to Track RC Availability

Monitor these resources:

  1. OpenShift Release Controller: https://openshift-release.apps.ci.l2s4.p1.openshiftapps.com/
  2. Mirror Repository: https://mirror.openshift.com/pub/openshift-v4/x86_64/microshift/ocp/
  3. Brew Builds (VPN Required): https://brewweb.engineering.redhat.com/brew/packageinfo?packageID=82827

Current EC Version Information

If you want to use the latest available version, check 4.21.0-ec.3:

RPM Packages

Bootc Images

Notes

  • 4.21 is currently in the Engineering Candidate phase
  • RC versions will be created after branch cutoff
  • EC versions are suitable for development and testing but are considered dev-preview quality
  • Use /microshift-release-versions 4.21.0-ec.3 to get detailed information about the latest EC version

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 16, 2025
@openshift-ci openshift-ci bot requested review from jerpeter1 and pmtk December 16, 2025 09:36
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 16, 2025
2. Use WebFetch to verify the directory exists and list packages

**For RC versions**:
1. Check mirror.openshift.com for ocp packages:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you mean rc packages instead of ocp ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, I mean ocp, because the packages are under ocp dir for RC: https://mirror.openshift.com/pub/openshift-v4/x86_64/microshift/ocp/

for EC they are under ocp-dev-preview

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay, but i feel the meaning completely changes when we read it it implies that we are checking for ocp packages and not microshift rc packages afaiu, but if you feel this is right, i am fine.

agullon and others added 3 commits December 17, 2025 09:12
Co-authored-by: Gregory Giguashvili <85498834+ggiguash@users.noreply.github.com>
@ggiguash
Copy link
Contributor

/lgtm
/verified by manual-testing

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Dec 17, 2025
@openshift-ci-robot
Copy link

@ggiguash: This PR has been marked as verified by manual-testing.

Details

In response to this:

/lgtm
/verified by manual-testing

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 17, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 17, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, ggiguash

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 17, 2025

@agullon: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 993bc85 into openshift:main Dec 17, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants