Skip to content

[release-4.22] NO-ISSUE: Update common_versions.sh#6110

Merged
openshift-merge-bot[bot] merged 1 commit intomainfrom
common-versions-update-release-4.22
Jan 20, 2026
Merged

[release-4.22] NO-ISSUE: Update common_versions.sh#6110
openshift-merge-bot[bot] merged 1 commit intomainfrom
common-versions-update-release-4.22

Conversation

@microshift-rebase-script
Copy link
Contributor

No description provided.

@openshift-ci-robot
Copy link

@microshift-rebase-script[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

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 Jan 20, 2026
@openshift-ci openshift-ci bot requested review from copejon and jerpeter1 January 20, 2026 05:12
@pacevedom
Copy link
Contributor

/retest

@agullon
Copy link
Contributor

agullon commented Jan 20, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 20, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 20, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, microshift-rebase-script[bot]

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 20, 2026
@pacevedom
Copy link
Contributor

/retest

@ggiguash
Copy link
Contributor

/verified by ci

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 20, 2026
@openshift-ci-robot
Copy link

@ggiguash: This PR has been marked as verified by ci.

Details

In response to this:

/verified by ci

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
Copy link

/retest-required

Remaining retests: 0 against base HEAD c60bc56 and 2 for PR HEAD 585d1bf in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 20, 2026

@microshift-rebase-script: 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 3edd8bb into main Jan 20, 2026
14 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the common-versions-update-release-4.22 branch January 20, 2026 20:39
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