Add go-mod-sync-kopia hook for oadp-vmdp rebase

[Joeavaikath]

Summary

Adds a new post-rebase hook go-mod-sync-kopia.sh that resets go.mod to the migtools/kopia source before go mod tidy runs. This prevents downstream carry commits from pinning stale dependency versions that drift behind kopia.

The oadp-vmdp rebase configs (oadp-1.6 and oadp-dev) are updated to run this hook as the first step in the hook chain, before go-mod-tidy and normalize-dockerfiles.

Problem

oadp-vmdp had downstream carry commits that explicitly pinned older dependency versions (e.g., grpc v1.79.3, otel v1.42.0). When rebased onto the current kopia base, these carry commits would overwrite kopia's newer versions, cascading stale pins across all transitive dependencies.

How it works

1. go-mod-sync-kopia.sh runs git checkout source/$REBASEBOT_SOURCE -- go.mod to restore kopia's go.mod
2. go-mod-tidy-and-commit.sh then runs go mod tidy, adding any extra deps oadp-vmdp needs on top of the kopia base

Test plan

• Tested locally with --local-hooks --dry-run — hook ran successfully, go mod tidy resolved to kopia-aligned versions
• Full rebase run created PR Merge https://github.com/migtools/kopia:oadp-1.6 (9ee940e) into oadp-1.6 migtools/oadp-vmdp#32 with correct dependency versions (grpc v1.81.1, otel v1.44.0, etc.)

[coderabbitai]

Warning

Review limit reached

@Joeavaikath, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 56 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 223f84b7-b558-4f4e-93af-a54bc3ead1d3

📥 Commits

Reviewing files that changed from the base of the PR and between 13a971d and 75afb65.

📒 Files selected for processing (3)

• rebase-configs/migtools_oadp_vmdp_oadp-1.6.env.sh
• rebase-configs/migtools_oadp_vmdp_oadp-dev.env.sh
• rebasebot-hook-scripts/go-mod-sync-kopia.sh

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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