OCPBUGS-80948: update velero replace to track oadp-1.6 branch

[jparrill]

What this PR does / why we need it

Updates the go.mod replace directive for Velero from a stale pseudo-version on the oadp-1.5 branch to the latest commit on the oadp-1.6 branch, which is the correct upstream branch for the oadp-1.6 release branch.

Before:

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

After:

replace github.com/vmware-tanzu/velero => github.com/openshift/velero v0.10.2-0.20260323191807-216dd62a1caf

This fixes two problems:

• Renovate/MintMaker failures: automated dependency updates resolved to incompatible upstream Velero versions (e.g. v1.2.0) that remove the v2alpha1 APIs the plugin depends on.
• Missing CVE/bug fixes: the stale oadp-1.5 replace was ~10 months behind, missing CVE and bug fixes available on the oadp-1.6 branch.

Additionally, sets the default DEPS_UPSTREAM_BRANCH to release-4.21 (instead of main) in the Makefile, dependency test, and update script, so that dependency validation checks against the correct hypershift upstream branch for the oadp-1.6 release.

This is the follow-up for the oadp-1.6 branch from #224 (which fixed main → oadp-dev).

Which issue(s) this PR fixes

Fixes: OCPBUGS-80948

Checklist

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs.
• This change includes unit tests.

🤖 Generated with Claude Code

[openshift-ci-robot]

@jparrill: This pull request references Jira Issue OCPBUGS-80948, which is invalid:

• expected the bug to be open, but it isn't
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead
• 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-80948 to depend on a bug in one of the following states: 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:

What this PR does / why we need it

Updates the go.mod replace directive for Velero from a stale pseudo-version on the oadp-1.5 branch to the latest commit on the oadp-1.6 branch, which is the correct upstream branch for the oadp-1.6 release branch.

Before:

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

After:

replace github.com/vmware-tanzu/velero => github.com/openshift/velero v0.10.2-0.20260323191807-216dd62a1caf

This fixes two problems:

• Renovate/MintMaker failures: automated dependency updates resolved to incompatible upstream Velero versions (e.g. v1.2.0) that remove the v2alpha1 APIs the plugin depends on.
• Missing CVE/bug fixes: the stale oadp-1.5 replace was ~10 months behind, missing CVE and bug fixes available on the oadp-1.6 branch.

This is the follow-up for the oadp-1.6 branch from #224 (which fixed main → oadp-dev).

Which issue(s) this PR fixes

Fixes: OCPBUGS-80948

Checklist

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs.
• This change includes unit tests.

🤖 Generated with Claude Code

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.

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)

• do-not-merge/work-in-progress

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1ac28e7e-6297-458c-a91c-71c94615f62b

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[jparrill]

Please @kaovilai do you mind review the oadp version set in the Makefile vs the ocp release assigned?.
btw, I know I need to add the tests to the release repo. I will put a hold until that happens

[jparrill]

/hold

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jparrill, kaovilai, weshayutin

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 [jparrill,kaovilai]

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

[openshift-ci]

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