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

[redhat-chai-bot]

Summary

Backport to release-4.22: 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-123142
• Original main PR: OCPBUGS-114428: Update build-machinery-go vendor dependency #260 (merged)

---

AI-generated. Review for accuracy.

@sdodson requested in Slack thread

Warning

Content scanning did not attest this change.
The scanner could not produce a verdict for the pushed content (never_attempted), so it has not been checked for credentials or malware.
Content scanning currently fails open, so this did not hold the change request for review — please review the diff with that in mind.

[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: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: e34aef6b-fe5e-44fe-9b74-5fa84ccab25c

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-123142, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• 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-122387 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-122387 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0
• bug has dependents

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

Details

In response to this:

Summary

Backport to release-4.22: 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-123142
• Original main PR: OCPBUGS-114428: Update build-machinery-go vendor dependency #260 (merged)

---

AI-generated. Review for accuracy.

@sdodson requested in Slack thread

[!WARNING]
Content scanning did not attest this change.
The scanner could not produce a verdict for the pushed content (never_attempted), so it has not been checked for credentials or malware.
Content scanning currently fails open, so this did not hold the change request for review — please review the diff with that in mind.

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 NOT APPROVED

This pull-request has been approved by: redhat-chai-bot
Once this PR has been reviewed and has the lgtm label, please assign ibihim for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci]

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]

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

[openshift-ci-robot]

@redhat-chai-bot: This pull request references Jira Issue OCPBUGS-114426, 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.22.0) matches configured target version for branch (4.22.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-122387 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-122387 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0
• bug has dependents

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

Details

In response to this:

Summary

Backport to release-4.22: 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-123142
• Original main PR: OCPBUGS-114428: Update build-machinery-go vendor dependency #260 (merged)

---

AI-generated. Review for accuracy.

@sdodson requested in Slack thread

[!WARNING]
Content scanning did not attest this change.
The scanner could not produce a verdict for the pushed content (never_attempted), so it has not been checked for credentials or malware.
Content scanning currently fails open, so this did not hold the change request for review — please review the diff with that in mind.

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

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

• openshift/service-ca-operator#377
• openshift/openshift-apiserver#685
• openshift/cluster-etcd-operator#1704
• openshift/oc#2399
• openshift/cluster-config-operator#503
• openshift/oauth-server#263
• openshift/cluster-kube-controller-manager-operator#969

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

• openshift/cluster-authentication-operator#1000 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.

Details

In response to this:

Summary

Backport to release-4.22: 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-123142
• Original main PR: OCPBUGS-114428: Update build-machinery-go vendor dependency #260 (merged)

---

AI-generated. Review for accuracy.

@sdodson requested in Slack thread

[!WARNING]
Content scanning did not attest this change.
The scanner could not produce a verdict for the pushed content (never_attempted), so it has not been checked for credentials or malware.
Content scanning currently fails open, so this did not hold the change request for review — please review the diff with that in mind.

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]

Fix included in release 4.22.0-0.nightly-2026-09-15-174544

[openshift-merge-robot]

Fix included in release 4.22.0-0.nightly-2026-09-21-030256