OCPBUGS-88416 OCPBUGS-88398: Bump Axios to fix CVE-2026-44486. Requires a Patch of axios 0.33.0 types to be compatible with old version of TS by rhdmalone · Pull Request #16793 · openshift/console

rhdmalone · 2026-07-21T16:52:46Z

OCPBUGS-88416: Bump Axios to fix CVE-2026-44486. Requires a Patch of axios 0.33.0 types to be compatible with an older version of TypeScript
Fixes CVE-2026-44486.
https://redhat.atlassian.net/browse/OCPBUGS-88416

How this patch was generated:
Step 1:
From frontend/:

Point deps at unpatched 0.33.0 temporarily i.e. In frontend/package.json:
Dependency:
"axios": "0.33.0"

Step 2:
cd frontend
yarn install
yarn patch axios@npm:0.33.0
Yarn prints a temp folder path.

For example:

yarn patch axios@npm:0.33.0
➤ YN0000: Package axios@npm:0.33.0 got extracted with success!
➤ YN0000: You can now edit the following folder: /private/var/folders/xh/64_dr2_j14s6q3vdq008bj9r0000gn/T/xfs-9ac099cb/user
➤ YN0000: Once you are done run yarn patch-commit -s /private/var/folders/xh/64_dr2_j14s6q3vdq008bj9r0000gn/T/xfs-9ac099cb/user and Yarn will store a patchfile based on your changes.
➤ YN0000: Done in 0s 23ms

Apply the same TypeScript fix in that folder’s index.d.ts
For example:
get the directory that is listed e.g./private/var/folders/xh/64_dr2_j14s6q3vdq008bj9r0000gn/T/xfs-8bb6f632/user
in that folder, edit and save the file index.d.ts
replace
type MethodsHeaders = {
[Key in Method as Lowercase]: AxiosHeaders;
};
with
type LowercaseMethod =
| 'get' | 'delete' | 'head' | 'options' | 'post'
| 'put' | 'patch' | 'purge' | 'link' | 'unlink';

type MethodsHeaders = {
[Key in LowercaseMethod]?: AxiosHeaders;
};

Step 3:
Apply changes:
yarn patch-commit -s /private/var/folders/xh/64_dr2_j14s6q3vdq008bj9r0000gn/T/xfs-9ac099cb/user
yarn install
yarn build

Step 4:
Add and commit changes etc
to determine the name of the patch, find it in the folder .yarn/patches - it will start with the name axios-npm-0.33.0

git add .yarn/patches/axios-npm-0.33.0-023deda7e4.patch
git add package.json
git add yarn.lock
git commit -m "OCPBUGS-88416: Bump Axios to fix CVE-2026-44486. Requires a Patch of axios 0.33.0 types to be compatible with older version of TypeScript"
git push

Testing
in the main console folder,
Test 1
./build-frontend.sh > test-4.12.axios-bump.txt
The output file was anlaysed by Claude:
Verdict: PASS — ./build-frontend.sh succeeded on release-4.12-260721 with the axios 0.33.0 Yarn type patch.

Test 2
./build-demos.sh > test-4.12-build-demos.txt
The output file was anlaysed by Claude:
Verdict: PASS - webpack 5.73.0 compiled successfully in 5628 ms

…axios 0.33.0 types to be compatible with older version of TypeScript

openshift-merge-bot · 2026-07-21T16:52:48Z

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

openshift-ci-robot · 2026-07-21T16:52:53Z

@rhdmalone: This pull request references Jira Issue OCPBUGS-88416, which is invalid:

expected dependent Jira Issue OCPBUGS-88410 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

OCPBUGS-88416: Bump Axios to fix CVE-2026-44486. Requires a Patch of axios 0.33.0 types to be compatible with an older version of TypeScript
Fixes CVE-2026-44486.
https://redhat.atlassian.net/browse/OCPBUGS-88416

How this patch was generated:
Step 1:
From frontend/:

Point deps at unpatched 0.33.0 temporarily i.e. In frontend/package.json:
Dependency:
"axios": "0.33.0"

Step 2:
cd frontend
yarn install
yarn patch axios@npm:0.33.0
Yarn prints a temp folder path.

For example:

yarn patch axios@npm:0.33.0
➤ YN0000: Package axios@npm:0.33.0 got extracted with success!
➤ YN0000: You can now edit the following folder: /private/var/folders/xh/64_dr2_j14s6q3vdq008bj9r0000gn/T/xfs-9ac099cb/user
➤ YN0000: Once you are done run yarn patch-commit -s /private/var/folders/xh/64_dr2_j14s6q3vdq008bj9r0000gn/T/xfs-9ac099cb/user and Yarn will store a patchfile based on your changes.
➤ YN0000: Done in 0s 23ms

Apply the same TypeScript fix in that folder’s index.d.ts
For example:
get the directory that is listed e.g./private/var/folders/xh/64_dr2_j14s6q3vdq008bj9r0000gn/T/xfs-8bb6f632/user
in that folder, edit and save the file index.d.ts
replace
type MethodsHeaders = {
[Key in Method as Lowercase]: AxiosHeaders;
};
with
type LowercaseMethod =
| 'get' | 'delete' | 'head' | 'options' | 'post'
| 'put' | 'patch' | 'purge' | 'link' | 'unlink';

type MethodsHeaders = {
[Key in LowercaseMethod]?: AxiosHeaders;
};

Step 3:
Apply changes:
yarn patch-commit -s /private/var/folders/xh/64_dr2_j14s6q3vdq008bj9r0000gn/T/xfs-9ac099cb/user
yarn install
yarn build

Step 4:
Add and commit changes etc
to determine the name of the patch, find it in the folder .yarn/patches - it will start with the name axios-npm-0.33.0

git add .yarn/patches/axios-npm-0.33.0-023deda7e4.patch
git add package.json
git add yarn.lock
git commit -m "OCPBUGS-88416: Bump Axios to fix CVE-2026-44486. Requires a Patch of axios 0.33.0 types to be compatible with older version of TypeScript"
git push

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.

coderabbitai · 2026-07-21T16:52:54Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 7582c43e-6876-4e8c-82af-5507ab9aeeb4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

Pranavgarud06 · 2026-07-22T14:22:40Z

/retitle OCPBUGS-88416 OCPBUGS-88398: Bump Axios to fix CVE-2026-44486. Requires a Patch of axios 0.33.0 types to be compatible with old version of TS
#16793

openshift-ci-robot · 2026-07-22T14:22:57Z

@rhdmalone: This pull request references Jira Issue OCPBUGS-88416, which is invalid:

expected dependent Jira Issue OCPBUGS-88410 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-88398, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.12.z) matches configured target version for branch (4.12.z)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-88391 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-88391 targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

OCPBUGS-88416: Bump Axios to fix CVE-2026-44486. Requires a Patch of axios 0.33.0 types to be compatible with an older version of TypeScript
Fixes CVE-2026-44486.
https://redhat.atlassian.net/browse/OCPBUGS-88416

How this patch was generated:
Step 1:
From frontend/:

Point deps at unpatched 0.33.0 temporarily i.e. In frontend/package.json:
Dependency:
"axios": "0.33.0"

Step 2:
cd frontend
yarn install
yarn patch axios@npm:0.33.0
Yarn prints a temp folder path.

For example:

yarn patch axios@npm:0.33.0
➤ YN0000: Package axios@npm:0.33.0 got extracted with success!
➤ YN0000: You can now edit the following folder: /private/var/folders/xh/64_dr2_j14s6q3vdq008bj9r0000gn/T/xfs-9ac099cb/user
➤ YN0000: Once you are done run yarn patch-commit -s /private/var/folders/xh/64_dr2_j14s6q3vdq008bj9r0000gn/T/xfs-9ac099cb/user and Yarn will store a patchfile based on your changes.
➤ YN0000: Done in 0s 23ms

Apply the same TypeScript fix in that folder’s index.d.ts
For example:
get the directory that is listed e.g./private/var/folders/xh/64_dr2_j14s6q3vdq008bj9r0000gn/T/xfs-8bb6f632/user
in that folder, edit and save the file index.d.ts
replace
type MethodsHeaders = {
[Key in Method as Lowercase]: AxiosHeaders;
};
with
type LowercaseMethod =
| 'get' | 'delete' | 'head' | 'options' | 'post'
| 'put' | 'patch' | 'purge' | 'link' | 'unlink';

type MethodsHeaders = {
[Key in LowercaseMethod]?: AxiosHeaders;
};

Step 3:
Apply changes:
yarn patch-commit -s /private/var/folders/xh/64_dr2_j14s6q3vdq008bj9r0000gn/T/xfs-9ac099cb/user
yarn install
yarn build

Step 4:
Add and commit changes etc
to determine the name of the patch, find it in the folder .yarn/patches - it will start with the name axios-npm-0.33.0

git add .yarn/patches/axios-npm-0.33.0-023deda7e4.patch
git add package.json
git add yarn.lock
git commit -m "OCPBUGS-88416: Bump Axios to fix CVE-2026-44486. Requires a Patch of axios 0.33.0 types to be compatible with older version of TypeScript"
git push

Testing
in the main console folder,
Test 1
./build-frontend.sh > test-4.12.axios-bump.txt
The output file was anlaysed by Claude:
Verdict: PASS — ./build-frontend.sh succeeded on release-4.12-260721 with the axios 0.33.0 Yarn type patch.

Test 2
./build-demos.sh > test-4.12-build-demos.txt
The output file was anlaysed by Claude:
Verdict: PASS - webpack 5.73.0 compiled successfully in 5628 ms

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.

rhdmalone · 2026-08-05T08:51:12Z

/jira refresh

openshift-ci-robot · 2026-08-05T08:51:18Z

@rhdmalone: This pull request references Jira Issue OCPBUGS-88416, which is invalid:

expected dependent Jira Issue OCPBUGS-88410 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-88398, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.12.z) matches configured target version for branch (4.12.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-88391 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-88391 targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

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.

logonoff · 2026-08-05T14:08:12Z

/label backport-risk-assessed

rhdmalone · 2026-08-06T08:41:26Z

/jira refresh

openshift-ci-robot · 2026-08-06T08:41:34Z

@rhdmalone: This pull request references Jira Issue OCPBUGS-88416, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.12.z) matches configured target version for branch (4.12.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-88410 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-88410 targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

This pull request references Jira Issue OCPBUGS-88398, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.12.z) matches configured target version for branch (4.12.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-88391 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-88391 targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

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.

rhdmalone · 2026-08-06T08:42:00Z

/verified by CI

openshift-ci-robot · 2026-08-06T08:42:12Z

@rhdmalone: 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.

germanparente · 2026-08-06T08:53:46Z

this has been already approved:

/lgtm

openshift-merge-bot · 2026-08-06T08:54:23Z

Scheduling required tests:
/test e2e-gcp-console

openshift-ci · 2026-08-06T08:54:24Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: germanparente, logonoff, rhdmalone

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:

~~frontend/OWNERS~~ [logonoff]

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

rhdmalone · 2026-08-06T11:10:47Z

/test e2e-gcp-console

rhdmalone · 2026-08-06T14:12:00Z

/test e2e-gcp-console

openshift-merge-bot · 2026-08-06T16:15:50Z

/retest-required

Remaining retests: 0 against base HEAD 61a6645 and 2 for PR HEAD b62301c in total

rhdmalone · 2026-08-07T08:34:10Z

/test e2e-gcp-console

rhdmalone · 2026-08-07T12:11:53Z

/test e2e-gcp-console

rhdmalone · 2026-08-07T12:13:04Z

analysis of failing test e2e-gcp-console by Sustaining Agentic Bot:
Retry with /retest. This is a transient timing flake in the topology empty-state assertion — not caused by changes in PR #16793. All ~350 other tests in Protractor, Cypress core suites, OLM, Helm, and Knative passed cleanly.

rhdmalone · 2026-08-07T16:30:07Z

/test e2e-gcp-console

rhdmalone · 2026-08-10T13:01:19Z

/test e2e-gcp-console

rhdmalone · 2026-08-10T14:34:11Z

@germanparente I asked the sustaining agentic bot to analyse the last failure for e2e-gcp-console:
The issues were due to resource exhaustion and were not created by the PR:

GCP compute resource exhaustion in zone us-central1-f caused the cluster installation to fail — the e2-custom-6-16384 VM instance type was unavailable in that zone at the time of the run.
:
"During the pre phase, the OpenShift IPI installer invoked Terraform to provision the GCP infrastructure. When attempting to create the third control-plane master node (module.master.google_compute_instance.master[2]) in zone us-central1-f, GCP returned an insufficient resources error for the e2-custom-6-16384 custom VM type. The installer exited with code 4 (infrastructure error)."

Recommendation
Infra flake — retry with /retest or /retest-required

germanparente · 2026-08-10T14:36:57Z

since the test is failing and it's not related to this PR:

/override ci/prow/e2e-gcp-console

openshift-ci · 2026-08-10T14:37:31Z

@germanparente: Overrode contexts on behalf of germanparente: ci/prow/e2e-gcp-console

Details

In response to this:

since the test is failing and it's not related to this PR:

/override ci/prow/e2e-gcp-console

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.

openshift-ci · 2026-08-10T14:37:34Z

@rhdmalone: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gcp-console	`b62301c`	link	true	`/test e2e-gcp-console`

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-ci-robot · 2026-08-10T14:42:56Z

@rhdmalone: Jira Issue Verification Checks: Jira Issue OCPBUGS-88416
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-88416 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Jira Issue Verification Checks: Jira Issue OCPBUGS-88398
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-88398 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

OCPBUGS-88416: Bump Axios to fix CVE-2026-44486. Requires a Patch of axios 0.33.0 types to be compatible with an older version of TypeScript
Fixes CVE-2026-44486.
https://redhat.atlassian.net/browse/OCPBUGS-88416

How this patch was generated:
Step 1:
From frontend/:

Point deps at unpatched 0.33.0 temporarily i.e. In frontend/package.json:
Dependency:
"axios": "0.33.0"

Step 2:
cd frontend
yarn install
yarn patch axios@npm:0.33.0
Yarn prints a temp folder path.

For example:

yarn patch axios@npm:0.33.0
➤ YN0000: Package axios@npm:0.33.0 got extracted with success!
➤ YN0000: You can now edit the following folder: /private/var/folders/xh/64_dr2_j14s6q3vdq008bj9r0000gn/T/xfs-9ac099cb/user
➤ YN0000: Once you are done run yarn patch-commit -s /private/var/folders/xh/64_dr2_j14s6q3vdq008bj9r0000gn/T/xfs-9ac099cb/user and Yarn will store a patchfile based on your changes.
➤ YN0000: Done in 0s 23ms

Apply the same TypeScript fix in that folder’s index.d.ts
For example:
get the directory that is listed e.g./private/var/folders/xh/64_dr2_j14s6q3vdq008bj9r0000gn/T/xfs-8bb6f632/user
in that folder, edit and save the file index.d.ts
replace
type MethodsHeaders = {
[Key in Method as Lowercase]: AxiosHeaders;
};
with
type LowercaseMethod =
| 'get' | 'delete' | 'head' | 'options' | 'post'
| 'put' | 'patch' | 'purge' | 'link' | 'unlink';

type MethodsHeaders = {
[Key in LowercaseMethod]?: AxiosHeaders;
};

Step 3:
Apply changes:
yarn patch-commit -s /private/var/folders/xh/64_dr2_j14s6q3vdq008bj9r0000gn/T/xfs-9ac099cb/user
yarn install
yarn build

Step 4:
Add and commit changes etc
to determine the name of the patch, find it in the folder .yarn/patches - it will start with the name axios-npm-0.33.0

git add .yarn/patches/axios-npm-0.33.0-023deda7e4.patch
git add package.json
git add yarn.lock
git commit -m "OCPBUGS-88416: Bump Axios to fix CVE-2026-44486. Requires a Patch of axios 0.33.0 types to be compatible with older version of TypeScript"
git push

Testing
in the main console folder,
Test 1
./build-frontend.sh > test-4.12.axios-bump.txt
The output file was anlaysed by Claude:
Verdict: PASS — ./build-frontend.sh succeeded on release-4.12-260721 with the axios 0.33.0 Yarn type patch.

Test 2
./build-demos.sh > test-4.12-build-demos.txt
The output file was anlaysed by Claude:
Verdict: PASS - webpack 5.73.0 compiled successfully in 5628 ms

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-merge-robot · 2026-08-11T07:11:05Z

Fix included in release 4.12.0-0.nightly-2026-08-11-003124

OCPBUGS-88416: Bump Axios to fix CVE-2026-44486. Requires a Patch of …

b62301c

…axios 0.33.0 types to be compatible with older version of TypeScript

openshift-ci Bot requested review from cajieh and rhamilto July 21, 2026 16:53

logonoff approved these changes Aug 5, 2026

View reviewed changes

openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Aug 5, 2026

openshift-ci Bot assigned sanketpathak Aug 5, 2026

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 5, 2026

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 6, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 6, 2026

openshift-ci Bot assigned germanparente Aug 6, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 6, 2026

openshift-merge-bot Bot merged commit 1271391 into openshift:release-4.12 Aug 10, 2026
7 checks passed

rhdmalone deleted the release-4.12-260721 branch August 10, 2026 14:47

Uh oh!

Conversation

rhdmalone commented Jul 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-merge-bot Bot commented Jul 21, 2026

Uh oh!

openshift-ci-robot commented Jul 21, 2026

Uh oh!

coderabbitai Bot commented Jul 21, 2026

Review skipped

Uh oh!

Pranavgarud06 commented Jul 22, 2026

Uh oh!

openshift-ci-robot commented Jul 22, 2026

Uh oh!

rhdmalone commented Aug 5, 2026

Uh oh!

openshift-ci-robot commented Aug 5, 2026

Uh oh!

logonoff commented Aug 5, 2026

Uh oh!

rhdmalone commented Aug 6, 2026

Uh oh!

openshift-ci-robot commented Aug 6, 2026

Uh oh!

rhdmalone commented Aug 6, 2026

Uh oh!

openshift-ci-robot commented Aug 6, 2026

Uh oh!

germanparente commented Aug 6, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 6, 2026

Uh oh!

openshift-ci Bot commented Aug 6, 2026

Uh oh!

rhdmalone commented Aug 6, 2026

Uh oh!

rhdmalone commented Aug 6, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 6, 2026

Uh oh!

rhdmalone commented Aug 7, 2026

Uh oh!

rhdmalone commented Aug 7, 2026

Uh oh!

rhdmalone commented Aug 7, 2026

Uh oh!

rhdmalone commented Aug 7, 2026

Uh oh!

rhdmalone commented Aug 10, 2026

Uh oh!

rhdmalone commented Aug 10, 2026

Uh oh!

germanparente commented Aug 10, 2026

Uh oh!

openshift-ci Bot commented Aug 10, 2026

Uh oh!

openshift-ci Bot commented Aug 10, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Aug 10, 2026

Uh oh!

openshift-merge-robot commented Aug 11, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

rhdmalone commented Jul 21, 2026 •

edited

Loading