Skip to content

ESO-400: Updates the latest bundle images in 4.19 - 5.0 OCP catalogs - #327

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
bharath-b-rh:main
Jul 8, 2026
Merged

ESO-400: Updates the latest bundle images in 4.19 - 5.0 OCP catalogs#327
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
bharath-b-rh:main

Conversation

@bharath-b-rh

@bharath-b-rh bharath-b-rh commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

The PR is for updating the v1.2.0 prod bundle image in OCP 4.19 - 5.0 OCP catalogs.

$ podman inspect registry.redhat.io/external-secrets-operator/external-secrets-operator-bundle@sha256:502364a848394debef14f079a5a84e3a472861fc802575a0bc662bebb832dc26 | grep -E "\"version\"|io.openshift.build.commit.url" -m2
                    "io.openshift.build.commit.url": "https://github.com/openshift/external-secrets-operator-release/commit/d290f41a2a4f25703189dc44ab7389930f9493c2",
                    "version": "v1.2.0"

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 25, 2026
@openshift-ci-robot

openshift-ci-robot commented Jun 25, 2026

Copy link
Copy Markdown

@bharath-b-rh: This pull request references ESO-400 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 task to target either version "5.0." or "openshift-5.0.", but it targets "eso-1.2" instead.

Details

In response to this:

The PR is for updating the v1.2.0 prod bundle image in OCP 4.19 - 5.0 OCP catalogs.

$ podman inspect registry.redhat.io/external-secrets-operator/external-secrets-operator-bundle@sha256:7bd8eefae992e5dd293e5ce7bf016459331018e3d7ed118d1503f7fcb05620e0 | grep -E "\"version\"|io.openshift.build.commit.url" -m2
                   "io.openshift.build.commit.url": "https://github.com/openshift/external-secrets-operator-release/commit/3f90c5ab1536b0c3e7dadb9ff2923e39ed135c70",
                   "version": "v1.2.0"

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 requested review from TrilokGeer and mytreya-rh June 25, 2026 11:36
@openshift-ci

openshift-ci Bot commented Jun 25, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bharath-b-rh

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 Jun 25, 2026
@bharath-b-rh

Copy link
Copy Markdown
Contributor Author

/hold

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 26, 2026
@bharath-b-rh
bharath-b-rh marked this pull request as draft June 26, 2026 12:36
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 26, 2026
@bharath-b-rh
bharath-b-rh force-pushed the main branch 2 times, most recently from 1f55922 to fee0803 Compare June 26, 2026 13:46
@bharath-b-rh
bharath-b-rh marked this pull request as ready for review July 8, 2026 11:29
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 8, 2026
@openshift-ci
openshift-ci Bot requested a review from swghosh July 8, 2026 11:29
@bharath-b-rh

Copy link
Copy Markdown
Contributor Author

/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 8, 2026
@mytreya-rh

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 8, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit 022ce67 into openshift:main Jul 8, 2026
11 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.

3 participants