Skip to content

MCO-1614: API bump for PinnedImageSet v1#314

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift:masterfrom
RishabhSaini:pisAPI
Mar 24, 2025
Merged

MCO-1614: API bump for PinnedImageSet v1#314
openshift-merge-bot[bot] merged 2 commits intoopenshift:masterfrom
RishabhSaini:pisAPI

Conversation

@RishabhSaini
Copy link
Copy Markdown
Contributor

@RishabhSaini RishabhSaini commented Mar 20, 2025

Pulling in changes for openshift/api#2198

@openshift-ci openshift-ci Bot requested review from JoelSpeed and bertinatto March 20, 2025 19:37
@RishabhSaini RishabhSaini changed the title Bumping API to latest to include PIS v1 API bump for PinnedImageSet v1 Mar 20, 2025
@RishabhSaini
Copy link
Copy Markdown
Contributor Author

/assign @JoelSpeed

@RishabhSaini RishabhSaini changed the title API bump for PinnedImageSet v1 MCO-1614: API bump for PinnedImageSet v1 Mar 20, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 20, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 20, 2025

@RishabhSaini: This pull request references MCO-1614 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Pulling in changes for openshift/api#2198

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.

Copy link
Copy Markdown
Member

@bertinatto bertinatto left a comment

Choose a reason for hiding this comment

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

Could you keep the generated changes in a separate commit?

@JoelSpeed
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 24, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, RishabhSaini

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 Mar 24, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 24, 2025

@RishabhSaini: 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 f0faeb0 into openshift:master Mar 24, 2025
3 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants