[release-4.18] OCPBUGS-103472: Replace golang.org/x/net with github.com/openshift-sustaining/net@v0.35.0-sec.3 - #153
Conversation
…staining/net@v0.35.0-sec.3 to address CVE-2026-33814 Signed-off-by: Venkata Charan Sunku <vsunku@redhat.com>
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
@sunku5494: This pull request references Jira Issue OCPBUGS-103472, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
/lgtm |
|
Scheduling required tests: |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: shannon, sunku5494 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
The get_tools.sh installs golint into BIN_DIR via GOBIN, but check_golint.sh invokes it as a bare command. On the Go 1.22 builder (release-4.18) BIN_DIR is not in PATH, causing 'golint: command not found'. Exporting PATH fixes this consistently across all Go versions.
|
/test pull-ci-openshift-network-metrics-daemon-release-4.18-unit |
|
New changes are detected. LGTM label has been removed. |
|
@sunku5494: The specified target(s) for The following commands are available to trigger optional jobs: Use DetailsIn 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 kubernetes-sigs/prow repository. |
|
@sunku5494: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
address CVE-2026-33814