ci: reduce update-builder schedule from hourly to every 4 hours

[Ankitsinghsisodya]

Problem

update-builder.yaml runs on an hourly cron (0 * * * *), while all other update workflows use 0 */4 * * * (every 4 hours) or daily. The builder image is published by an external team and does not change hourly, so the extra runs provide no benefit while consuming ~18 runner-hours/day.

Fix

Change the cron from 0 * * * * to 0 */4 * * * to match the cadence of all other update workflows.

Closes #3563

[knative-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Ankitsinghsisodya
Once this PR has been reviewed and has the lgtm label, please assign matzew for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[knative-prow]

Hi @Ankitsinghsisodya. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[Copilot]

Pull request overview

This PR reduces the run frequency of the update-builder scheduled GitHub Actions workflow to better align with the cadence of other update workflows and to avoid unnecessary runner usage.

Changes:

• Update .github/workflows/update-builder.yaml cron schedule from hourly (0 * * * *) to every 4 hours (0 */4 * * *).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.23%. Comparing base (d54878b) to head (a9a809f).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3566      +/-   ##
==========================================
+ Coverage   53.76%   56.23%   +2.46%     
==========================================
  Files         180      180              
  Lines       20465    20465              
==========================================
+ Hits        11004    11509     +505     
+ Misses       8355     7756     -599     
- Partials     1106     1200      +94     

Flag	Coverage Δ
e2e	36.12% <ø> (ø)
e2e go	32.55% <ø> (ø)
e2e node	28.36% <ø> (-0.03%)	⬇️
e2e python	32.91% <ø> (ø)
e2e quarkus	28.50% <ø> (ø)
e2e rust	27.92% <ø> (ø)
e2e springboot	26.38% <ø> (ø)
e2e typescript	28.47% <ø> (-0.03%)	⬇️
e2e-config-ci	18.14% <ø> (ø)
integration	17.38% <ø> (?)
unit macos-14	43.37% <ø> (ø)
unit macos-latest	43.37% <ø> (ø)
unit ubuntu-24.04-arm	43.57% <ø> (ø)
unit ubuntu-latest	44.25% <ø> (ø)
unit windows-latest	43.39% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.