OCPBUGS-114426: Update build-machinery-go vendor dependency

[redhat-chai-bot]

Summary

Update github.com/openshift/build-machinery-go vendor dependency to v0.0.0-20260902143904-520f675c892b.

Changes

• Updated go.mod with the latest build-machinery-go version
• Ran go mod tidy
• Ran go mod vendor to update the vendored copy

Related

• OCPBUGS-114426: Bump golang builder to 1.26 and protobuf for 4.22 OCP CI and Nightlies

---

AI-generated. Review for accuracy.

@Prashanth684 requested in Slack thread

[coderabbitai]

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 YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Advanced

Run ID: 92d851a9-85c8-4282-8cd0-fe1cf6fbb9a3

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

---

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

[openshift-ci-robot]

@redhat-chai-bot: This pull request references Jira Issue OCPBUGS-114426, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-114426 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

Summary

Update github.com/openshift/build-machinery-go vendor dependency to v0.0.0-20260902143904-520f675c892b.

Changes

• Updated go.mod with the latest build-machinery-go version
• Ran go mod tidy
• Ran go mod vendor to update the vendored copy

Related

• OCPBUGS-114426: Bump golang builder to 1.26 and protobuf for 4.22 OCP CI and Nightlies

---

AI-generated. Review for accuracy.

@Prashanth684 requested in Slack thread

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-bot]

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

[ardaguclu]

/retest
/pipeline required

[openshift-merge-bot]

Scheduling required tests:
/test e2e-agnostic-ovn-cmd
/test e2e-aws-ovn
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-aws-ovn-upgrade

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-agent-compact-ipv4

[openshift-ci]

@redhat-chai-bot: 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.

[tchap]

/lgtm

[ardaguclu]

/approve
/label backport-risk-assessed
/verified by CI

[openshift-ci-robot]

@ardaguclu: This PR has been marked as verified by CI.

Details

In response to this:

/approve
/label backport-risk-assessed
/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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ardaguclu, redhat-chai-bot, tchap

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:

• OWNERS [ardaguclu]

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

[sdodson]

This fixes reconciliation prs, merging

[openshift-ci-robot]

@redhat-chai-bot: Jira Issue OCPBUGS-114426: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

• openshift/service-ca-operator#377 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-114426 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Details

In response to this:

Summary

Update github.com/openshift/build-machinery-go vendor dependency to v0.0.0-20260902143904-520f675c892b.

Changes

• Updated go.mod with the latest build-machinery-go version
• Ran go mod tidy
• Ran go mod vendor to update the vendored copy

Related

• OCPBUGS-114426: Bump golang builder to 1.26 and protobuf for 4.22 OCP CI and Nightlies

---

AI-generated. Review for accuracy.

@Prashanth684 requested in Slack thread

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.