NO-JIRA: feat: add renovate configuration

[jgbernalp]

Summary by CodeRabbit

• Chores
  • Added automated dependency update management with scheduled checks and controlled pull request limits.
  • Configured dependency version pinning, release-age safeguards, and grouped PatternFly updates.
  • Added vulnerability alert labeling and standardized security update commit messages.
  • Excluded selected dependencies and front-end packages from automated updates.

[openshift-ci-robot]

@jgbernalp: This pull request explicitly references no jira issue.

Details

In response to this:

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]

Warning

Review limit reached

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

Next review available in: 49 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 1753fa9c-0791-4772-a168-f9bc1f218186

📥 Commits

Reviewing files that changed from the base of the PR and between 2241c8a and b77b4d0.

📒 Files selected for processing (1)

• renovate.json

Walkthrough

The PR adds renovate.json with update scheduling, dependency pinning, package rules, vulnerability alert settings, and targeted Go and web dependency paths.

Changes

Renovate configuration

Layer / File(s)	Summary
Dependency update policies renovate.json	Configures Renovate scheduling, concurrency, version pinning, update paths, ignored packages, lock file maintenance, vulnerability alerts, release-age gating, disabled package updates, and PatternFly grouping.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: zhuje

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a Renovate configuration.
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	The commit adds only renovate.json and contains no Ginkgo or other test-title declarations, so no unstable test names are introduced.
Test Structure And Quality	✅ Passed	The PR changes only renovate.json; no Ginkgo test files, imports, or It blocks are changed, so this test-structure check is not applicable.
Microshift Test Compatibility	✅ Passed	No Ginkgo e2e tests are added. PR adds only renovate.json configuration file, which is outside the scope of this check.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The patch adds only renovate.json; it adds no Ginkgo e2e tests or test changes that could make multi-node assumptions.
Topology-Aware Scheduling Compatibility	✅ Passed	The pull request changes only renovate.json; it adds no deployment manifests, operator code, controllers, or scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	The PR changes only renovate.json; no OTE binary or process-level Go code changed, so this stdout contract check is not applicable.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The pull request changes only renovate.json; it adds no Ginkgo e2e tests or test networking code to assess.
No-Weak-Crypto	✅ Passed	The pull request adds only renovate.json; its 56 added lines contain no weak algorithms, crypto APIs, custom crypto, or secret/token comparisons.
Container-Privileges	✅ Passed	The PR changes only renovate.json. It adds no container or Kubernetes manifest and no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, root, or allowPrivilegeEscalation setting.
No-Sensitive-Data-In-Logs	✅ Passed	The PR adds only renovate.json; it introduces no logging calls and contains no passwords, tokens, API keys, PII, hostnames, or customer data.

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@rennovate.json`:
- Line 1: Rename the configuration file from rennovate.json to the standard
renovate.json filename so Renovate discovers and applies the repository policy
without custom runner configuration.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 21e461cd-61af-4bcd-983c-2d2cf4dd20be

📥 Commits

Reviewing files that changed from the base of the PR and between 2241c8a and 3565eb6.

📒 Files selected for processing (1)

• rennovate.json

[PeterYurkovich]

Perhaps we can look at this as a follow up, but renovate does allow grouping updates, so we may be able to look into that to not be overwelmed

[coderabbitai]

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

[jgbernalp]

Perhaps we can look at this as a follow up, but renovate does allow grouping updates, so we may be able to look into that to not be overwelmed

yeah, I added some basic grouping but wanted to check after running it which others make sense.

[PeterYurkovich]

/lgtm

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@renovate.json`:
- Line 6: Add a Renovate package rule before the existing web package rules that
targets peer dependencies and preserves compatibility ranges, overriding the
global rangeStrategy pin for entries such as react-router-dom in
web/package.json. Keep the later web-specific rules unchanged.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: ea4688b6-79c7-469f-8458-cf3112b9dd22

📥 Commits

Reviewing files that changed from the base of the PR and between 2241c8a and b37efc4.

📒 Files selected for processing (1)

• renovate.json

[PeterYurkovich]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgbernalp, PeterYurkovich

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 [PeterYurkovich,jgbernalp]

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

[jgbernalp]

/label qe-approved

[jgbernalp]

/override ci/prow/e2e-agnostic-cmo

[openshift-ci]

@jgbernalp: Overrode contexts on behalf of jgbernalp: ci/prow/e2e-agnostic-cmo

Details

In response to this:

/override ci/prow/e2e-agnostic-cmo

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.

[openshift-ci]

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