ROX-35657: Replace pre-modules pseudo-versions with actual dependency versions (backport to release-1.9)

[guzalv]

Description

Backport of #1301 (ROX-35657, originally merged to master as cdef8fe) to release-1.9.

go.mod on release-1.9 still declares pre-Go-modules pseudo-versions for openshift/api (v0.0.1) and openshift/client-go (v0.0.1), redirected via replace directives to the real versions. replace directives don't propagate to consumers, so every downstream consumer (e.g. stackrox/stackrox) has to duplicate them in their own go.mod to avoid pulling broken pre-modules code — see the recent stackrox go mod tidy breakage caused by the orphaned compliance-sdk commit (mitigated separately by #1356 and the archive-gomod-20250925 tag), which resurfaced this same class of issue.

This backport declares the real resolved versions directly and drops the replace block, same as #1301 on master.

release-1.9 had already diverged from master on this file: openshift/client-go had been re-resolved to an indirect dependency, and openshift/api's only remaining require line was a stray duplicate still at the broken v0.0.1. Applied go mod tidy + go mod vendor after resolving conflicts so the module graph re-derives correctly for release-1.9's actual current dependency set (openshift/api direct, openshift/client-go indirect, both at real versions).

Motivation for landing this on release-1.9 specifically (rather than only on master): it lets stackrox/stackrox bump to a proper tagged release (e.g. a future v1.9.3) instead of pinning a master pseudo-version to get a go.mod without the legacy replace directives.

Testing

• go build ./... — clean
• go vet ./... — clean
• go test $(go list ./... | grep -v -E '/vendor/|/test|/examples') — all pass
• gofmt -l clean on all non-vendored changed files (vendored openshift/api/openshift/client-go source carries its own upstream formatting, unmodified by us)

🤖 Generated with Claude Code / OpenCode, reviewed by @guzalv

[openshift-ci]

Hi @guzalv. Thanks for your PR.

I'm waiting for a ComplianceAsCode member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[openshift-ci-robot]

@guzalv: This pull request references ROX-35657 which is a valid jira issue.

Details

In response to this:

Description

Backport of #1301 (ROX-35657, originally merged to master as cdef8fe) to release-1.9.

go.mod on release-1.9 still declares pre-Go-modules pseudo-versions for openshift/api (v0.0.1) and openshift/client-go (v0.0.1), redirected via replace directives to the real versions. replace directives don't propagate to consumers, so every downstream consumer (e.g. stackrox/stackrox) has to duplicate them in their own go.mod to avoid pulling broken pre-modules code — see the recent stackrox go mod tidy breakage caused by the orphaned compliance-sdk commit (mitigated separately by #1356 and the archive-gomod-20250925 tag), which resurfaced this same class of issue.

This backport declares the real resolved versions directly and drops the replace block, same as #1301 on master.

release-1.9 had already diverged from master on this file: openshift/client-go had been re-resolved to an indirect dependency, and openshift/api's only remaining require line was a stray duplicate still at the broken v0.0.1. Applied go mod tidy + go mod vendor after resolving conflicts so the module graph re-derives correctly for release-1.9's actual current dependency set (openshift/api direct, openshift/client-go indirect, both at real versions).

Motivation for landing this on release-1.9 specifically (rather than only on master): it lets stackrox/stackrox bump to a proper tagged release (e.g. a future v1.9.3) instead of pinning a master pseudo-version to get a go.mod without the legacy replace directives.

Testing

• go build ./... — clean
• go vet ./... — clean
• go test $(go list ./... | grep -v -E '/vendor/|/test|/examples') — all pass
• gofmt -l clean on all non-vendored changed files (vendored openshift/api/openshift/client-go source carries its own upstream formatting, unmodified by us)

🤖 Generated with Claude Code / OpenCode, reviewed by @guzalv

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.

[abushkin-redhat]

/ok-to-test

[yuumasato]

/ok-to-test

[yuumasato]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: guzalv, yuumasato

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 [yuumasato]

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

[yuumasato]

@guzalv Commit in this PR is not signed.

[openshift-ci]

New changes are detected. LGTM label has been removed.

[guzalv]

@guzalv Commit in this PR is not signed.

Thanks! Done