Skip to content

Pull requests: openshift/oc-mirror

New pull request New
15 Open 1,199 Closed
15 Open 1,199 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Reviews
Filter by reviews
No reviews Review required Approved review Changes requested
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Pull requests list

NO-JIRA: Bump v1 security-updates group, pinning filepath-securejoin to v0.5.1 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.
#1511 opened Aug 21, 2026 by aguidirh Contributor Loading…
@adolfo-ab
14
[release-4.19] OCPBUGS-105781: fix for CVE-2026-39829 jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. verified Signifies that the PR passed pre-merge verification criteria
#1510 opened Aug 21, 2026 by rhdmalone Loading…
1 task
9
Bump the oc-mirror-v1-security-updates group across 1 directory with 10 updates dependencies Pull requests that update a dependency file go Pull requests that update Go code ok-to-test Indicates a non-member PR verified by an org member that is safe to test.
#1508 opened Aug 20, 2026 by dependabot Bot Loading…
10
[release-4.20] OCPBUGS-105780: fix for CVE-2026-39829 jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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
#1506 opened Aug 19, 2026 by rhdmalone Loading…
1 task
@adolfo-ab
14
OCPBUGS-85713: set WorkingDir from --delete-yaml-file path jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test.
#1500 opened Aug 13, 2026 by shishind Loading…
1 of 2 tasks
10
OCPBUGS-78497: reject uppercase registry hostnames in docker destinations jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test.
#1499 opened Aug 12, 2026 by shishind Loading…
4 tasks
10
RFE-8713: allow Helm values for chart image discovery jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.
#1498 opened Aug 12, 2026 by Shraddhaa-28 Loading…
6 tasks
22
OCPBUGS-77670: Handle incomplete workspace directory structures gracefully jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#1464 opened Jul 6, 2026 by redhat-chai-bot Loading…
6
[release-4.22] OCPBUGS-92814: v1/e2e: reduce helm download flakiness approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#1455 opened Jun 26, 2026 by openshift-cherrypick-robot Loading…
@r4f4
6
OCPBUGS-90135: retry blob copy on dropped connections jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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.
#1454 opened Jun 25, 2026 by zaneb Member Loading…
@bfournie
8
Add releaseImageRepo and releaseComponentRepo to ImageSetConfiguration needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test.
#1452 opened Jun 24, 2026 by eb4x Loading…
1 task done
13
[release-4.22] OCPBUGS-90149: fix(helm): tolerate v-prefix version mismatch in disk-to-mirror jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#1448 opened Jun 18, 2026 by openshift-cherrypick-robot Loading…
@aguidirh
5
OCPBUGS-65718: Fixes the test-integration when running on ppc64le and arm64 jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#1431 opened Jun 5, 2026 by prb112 Contributor Loading…
1 of 6 tasks
@prb112
26
CLID-515: claude: add slash command to generate test cases and testing approach based on PR. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#1335 opened Jan 3, 2026 by nidangavali Contributor Loading…
2 of 6 tasks
17
WIP: Add gomock support approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#1102 opened Mar 3, 2025 by r4f4 Contributor Loading…
6 tasks
21
ProTip! Follow long discussions with comments:>50.