Skip to content

ROX-36225: Extend MintMaker schedule - #3580

Open
tommartensen wants to merge 3 commits into
masterfrom
tm/ROX-36225-extend-mintmaker-schedule
Open

ROX-36225: Extend MintMaker schedule#3580
tommartensen wants to merge 3 commits into
masterfrom
tm/ROX-36225-extend-mintmaker-schedule

Conversation

@tommartensen

Copy link
Copy Markdown
Contributor

No description provided.

@tommartensen tommartensen self-assigned this Aug 10, 2026
@tommartensen
tommartensen requested a review from a team as a code owner August 10, 2026 13:59
@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@tommartensen, 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: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 3ad41de4-a95b-4a0f-8721-085e3fd1be7d

📥 Commits

Reviewing files that changed from the base of the PR and between 9c000f0 and c01a023.

📒 Files selected for processing (1)
  • .github/renovate.json5
📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Updated automated dependency maintenance to run during a broader daily window.
    • Added clarification about the maintenance schedule and post-merge delay.

Walkthrough

The Renovate configuration changes the general and Tekton daily schedules from 03:00–07:00 UTC to 00:00–08:00 UTC. The general schedule comments now document the post-merge delay and the selected interval.

Changes

Renovate scheduling

Layer / File(s) Summary
Update Renovate schedules
.github/renovate.json5
The general and Tekton schedules now run daily from 00:00 through 08:00 UTC. Comments document the general schedule rationale and interval.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: msugakov

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive No pull request description was provided, so its relevance to the schedule change cannot be assessed. Add a brief description of the MintMaker schedule changes and the reason for extending the schedule.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the main change: extending the MintMaker schedule.
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.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch tm/ROX-36225-extend-mintmaker-schedule

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

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 @.github/renovate.json5:
- Around line 34-37: Align both Renovate schedule entries with the documented
0a.m.–8a.m. cutoff by changing each `* 0-8 * * *` expression in
`.github/renovate.json5` to `* 0-7 * * *`; keep the surrounding schedule
comments consistent with the before-08:00 UTC window.
🪄 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: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 38b66ee6-2df9-478b-be09-6b7ea294f5d7

📥 Commits

Reviewing files that changed from the base of the PR and between 3b9db54 and 9c000f0.

📒 Files selected for processing (1)
  • .github/renovate.json5

Comment thread .github/renovate.json5 Outdated
@openshift-ci

openshift-ci Bot commented Aug 10, 2026

Copy link
Copy Markdown

@github-actions[bot]: The /retest command does not accept any targets.
The following commands are available to trigger optional jobs:

/test e2e-tests
/test slim-e2e-tests

Use /test all to run all jobs.

Details

In response to this:

/retest scanner-on-push

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.

@tommartensen
tommartensen enabled auto-merge (squash) August 10, 2026 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant