Update openshift/velero replace directive to track correct branch

[kaovilai]

Problem

The go.mod replace directive for Velero currently points to a stale pseudo-version on the oadp-1.5 branch:

replace github.com/vmware-tanzu/velero => github.com/openshift/velero v0.10.2-0.20250514165055-8fbcf3a8da11

This resolves to commit 8fbcf3a8da11 (2025-05-14) on openshift/velero oadp-1.5.

This causes problems:

1. Renovate/MintMaker PRs fail because automated dependency updates resolve to incompatible Velero versions (e.g. v1.2.0) that remove APIs the plugin depends on (velero/pkg/apis/velero/v2alpha1). See PRs chore(deps): update non-k8s-go-dependencies (major) #215, chore(deps): update non-k8s-go-dependencies (major) #216.
2. The replace version falls behind the actual openshift/velero branch, which has since received CVE fixes and bug fixes.

Context

The OADP rebasebot config shows that openshift/velero is rebased from upstream vmware-tanzu/velero:main into branches like:

• oadp-dev (latest: 5ef912f4, 2026-03-23)
• oadp-1.6 (latest: 216dd62a, 2026-03-23)
• oadp-1.5 (latest: 1b8c9c44, 2026-03-17)

The hypershift-oadp-plugin should track the appropriate openshift/velero branch for its target OADP release.

Proposed Fix

For the main branch of hypershift-oadp-plugin (targeting OADP 1.6 / oadp-dev):

go mod edit -replace github.com/vmware-tanzu/velero=github.com/openshift/velero@oadp-1.6
go mod tidy
go mod vendor

Ensure the replace directive is updated whenever the openshift/velero branch receives new commits, either manually or via Renovate/MintMaker configuration that understands the replace.

Additional Notes

• The v2alpha1 API package must exist in whichever openshift/velero commit is used — verify before updating.
• Each release branch of hypershift-oadp-plugin should track the corresponding openshift/velero branch (e.g. oadp-1.5 branch → openshift/velero@oadp-1.5).

Note

Responses generated with Claude