ROSA-745: revert pilot fork renovate extends to openshift/boilerplate

[MitaliBhalla]

Summary

Reverts the #285 pilot change that pointed .github/renovate.json at MitaliBhalla/boilerplate#draft/rosa-745-gomod-batch-monday and restores the fleet-standard upstream extends:

"github>openshift/boilerplate//.github/renovate.json"

Unchanged: .github/dependabot.yml docker labels (lgtm/approved) and Mon 03:00 UTC schedule from #285.

Why

• Pilot fork is no longer needed; ROSA-745: MintMaker gomod batch + automerge via boilerplate renovate boilerplate#748 carries the gomod MintMaker config on upstream.
• Aligns ocm-agent-operator with other operators that inherit renovate from upstream boilerplate.

After merge

• Before #748 merges: upstream renovate is tekton-only (same as pre-pilot production boilerplate).
• After #748 merges: this repo picks up grouped gomod MintMaker rules automatically via extends (no fork).

Follow-up

• Close stale Dependabot gomod PR #240 if still open.
• Run boilerplate-update after #748 for standard.mk validate fix.

Test plan

• renovate.json validates against upstream boilerplate extends
• Dependency Dashboard updates after Konflux rescan
• No dependency on MitaliBhalla/boilerplate fork branch

Related

• Reverts pilot portion of ROSA-745: pilot boilerplate#748 automerge config (pre-fleet validation) #285 (renovate.json only)
• ROSA-745: MintMaker gomod batch + automerge via boilerplate renovate boilerplate#748
• ROSA-745

Made with Cursor

Summary by CodeRabbit

• Chores
  • Updated automated dependency management configuration to reference an alternate upstream source.

[openshift-ci-robot]

@MitaliBhalla: This pull request references ROSA-745 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the initiative to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

Reverts the #285 pilot change that pointed .github/renovate.json at MitaliBhalla/boilerplate#draft/rosa-745-gomod-batch-monday and restores the fleet-standard upstream extends:

"github>openshift/boilerplate//.github/renovate.json"

Unchanged: .github/dependabot.yml docker labels (lgtm/approved) and Mon 03:00 UTC schedule from #285.

Why

• Pilot fork is no longer needed; ROSA-745: MintMaker gomod batch + automerge via boilerplate renovate boilerplate#748 carries the gomod MintMaker config on upstream.
• Aligns ocm-agent-operator with other operators that inherit renovate from upstream boilerplate.

After merge

• Before #748 merges: upstream renovate is tekton-only (same as pre-pilot production boilerplate).
• After #748 merges: this repo picks up grouped gomod MintMaker rules automatically via extends (no fork).

Follow-up

• Close stale Dependabot gomod PR #240 if still open.
• Run boilerplate-update after #748 for standard.mk validate fix.

Test plan

• renovate.json validates against upstream boilerplate extends
• Dependency Dashboard updates after Konflux rescan
• No dependency on MitaliBhalla/boilerplate fork branch

Related

• Reverts pilot portion of ROSA-745: pilot boilerplate#748 automerge config (pre-fleet validation) #285 (renovate.json only)
• ROSA-745: MintMaker gomod batch + automerge via boilerplate renovate boilerplate#748
• ROSA-745

Made with Cursor

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]

Walkthrough

This PR updates .github/renovate.json to extend the official OpenShift boilerplate Renovate configuration. The extends field switches from a draft branch reference to the published boilerplate repository configuration.

Changes

Renovate Config

Layer / File(s)	Summary
Renovate extends configuration .github/renovate.json	The extends list changes from github>MitaliBhalla/boilerplate#draft/... to github>openshift/boilerplate//.github/renovate.json, using the official upstream configuration.

Possibly Related PRs

• openshift/ocm-agent-operator#285: Updates .github/renovate.json's extends setting; this PR restores the reference to the official openshift/boilerplate configuration after that temporary change.

Suggested Labels

approved, lgtm, jira/valid-reference

Suggested Reviewers

• vaidehi411
• xiaoyu74

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly references the main change: reverting the renovate configuration extends from a pilot fork back to the upstream openshift/boilerplate standard.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	All 87 Ginkgo test titles examined use static descriptive strings with no dynamic information like UUIDs, timestamps, generated suffixes, or node/namespace/IP addresses.
Test Structure And Quality	✅ Passed	PR only modifies .github/renovate.json configuration; no test code changes present, so Ginkgo test quality check is not applicable.
Microshift Test Compatibility	✅ Passed	PR only modifies .github/renovate.json (Renovate config); no Ginkgo e2e tests are added, so MicroShift test compatibility check does not apply.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR only modifies .github/renovate.json configuration file with no new Ginkgo e2e tests added, making SNO test compatibility check not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	Check does not apply: PR only modifies .github/renovate.json (tool config), not deployment manifests, operator code, or controllers with scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	PR changes only .github/renovate.json configuration file with no executable code, test code, or logging setup that could violate OTE stdout contract.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only modifies .github/renovate.json configuration; no Ginkgo e2e tests are added or modified, so IPv6/disconnected network test compatibility check does not apply.
No-Weak-Crypto	✅ Passed	The PR only modifies .github/renovate.json, a configuration file with no code. It contains no cryptographic implementations, weak crypto usage, or secret comparisons.
Container-Privileges	✅ Passed	PR only modifies .github/renovate.json, a Renovate dependency automation config. No container/K8s manifests or privilege escalation settings present.
No-Sensitive-Data-In-Logs	✅ Passed	PR modifies only .github/renovate.json configuration file with no logging statements or exposed sensitive data (passwords, tokens, API keys, PII, etc.).
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-ci]

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

[MitaliBhalla]

/retest

[devppratik]

/lgtm

[tkong-redhat]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: devppratik, MitaliBhalla, tkong-redhat

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 [tkong-redhat]

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