ROSA-745: boilerplate-update and enable MintMaker gomod

[MitaliBhalla]

Summary

• make boilerplate-update (includes boilerplate #748 dependabot template)
• .github/renovate.json — enabledManagers: [tekton, gomod] for MintMaker gomod PRs

Test plan

• CI green

Jira: ROSA-745

Summary by CodeRabbit

• Chores
  • Updated dependency management automation configuration to enable additional manager support for improved dependency handling.

[coderabbitai]

Caution

Review failed

An error occurred during the review process. Please try again later.

Walkthrough

The pull request updates .github/renovate.json to explicitly configure Renovate to enable the tekton and gomod managers via a new enabledManagers array. The extends array termination is adjusted with a trailing comma to support the additional configuration.

Changes

Renovate Configuration

Layer / File(s)	Summary
Enable tekton and gomod managers .github/renovate.json	A top-level enabledManagers array is added to explicitly enable tekton and gomod dependency managers, with the extends array adjusted to include a trailing comma.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ 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-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

• make boilerplate-update (includes boilerplate #748 dependabot template)
• .github/renovate.json — enabledManagers: [tekton, gomod] for MintMaker gomod PRs

Test plan

• CI green

Jira: ROSA-745

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MitaliBhalla

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

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

[MitaliBhalla]

/retest-required

[MitaliBhalla]

/retest-required

[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-required

[MitaliBhalla]

/retest-required

[xiaoyu74]

can see you've closed the previous #554 and created this new #555 , could you clarify a bit why #554 was closed and replaced by #555?

• I see ROSA-745: boilerplate-update and enable MintMaker gomod #555 no longer includes the e2e Dockerfile/Go 1.26/WORKDIR changes from ROSA-745: enable MintMaker gomod and docker-only Dependabot #554. Is that intentionally split out of this PR? If Konflux e2e still needs that fix, will it be handled separately?

• IIUC, boilerplate #748 moves gomod handling to MintMaker/Renovate, should this ROSA-745: boilerplate-update and enable MintMaker gomod #555 also remove the existing gomod block from MCVW’s .github/dependabot.yml? My concern is that ROSA-745: boilerplate-update and enable MintMaker gomod #555 enables MintMaker gomod, but if Dependabot gomod remains enabled, we may still have the duplicate gomod PR path that #748 is trying to avoid

[xiaoyu74]

Does this MCVW really needs this explicitly for MintMaker gomod to run, instead of relying only on the inherited boilerplate renovate config?

as you mentioned earlier pagerduty-operator was used as a reference case, but I want to understand whether this is a `Renovate/MintMaker merge behavior or a rollout workaround?

[xiaoyu74]

btw, can see we have one konflux CI job failed, once we understand the reduced scope in this new #555 and CI it's green, it should be much easier to review.