Fix publish workflow schedule to match intended cadence

The workflow defined only a single 12-minute cron, but the job's `if`
gated on an hourly cron string ("0 0-6,15-23 * * *") that was never
registered. So the hourly fallback never matched, and when
WORLDCUP26_LIVE was false the site stopped rebuilding entirely instead
of refreshing hourly.

Register two crons: an hourly tick that always runs, and a 10-minute
tick (:10-:50, excluding :00 to avoid double runs) that proceeds only
when WORLDCUP26_LIVE is true. Bump to 0.5.1.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: smach

.github/workflows/publish.yml

@@ -4,8 +4,11 @@ on:
   push:
     branches: [main]
   schedule:
-    # Every 12 minutes during match windows (15:00–06:00 UTC), skip overnight lull.
-    - cron: "0,12,24,36,48 0-6,15-23 * * *"
+    # Match window is 15:00-06:00 UTC (hours 15-23 and 0-6); skip the overnight lull.
+    # Hourly tick (top of the hour): always runs.
+    - cron: "0 0-6,15-23 * * *"
+    # Every 10 minutes (excluding :00, covered above): only runs when WORLDCUP26_LIVE is true.
+    - cron: "10,20,30,40,50 0-6,15-23 * * *"
   workflow_dispatch:
 
 permissions:
@@ -15,8 +18,8 @@ jobs:
   render:
     runs-on: ubuntu-latest
 
-    # The hourly tick and manual/push runs always proceed; the 10-min tick
-    # only proceeds when the repo variable WORLDCUP26_LIVE is "true".
+    # The hourly tick (cron "0 ...") and manual/push runs always proceed; the
+    # 10-min ticks only proceed when the repo variable WORLDCUP26_LIVE is "true".
     if: >
       github.event_name != 'schedule' ||
       github.event.schedule == '0 0-6,15-23 * * *' ||

DESCRIPTION

@@ -1,6 +1,6 @@
 Package: worldcup26
 Title: Access FIFA 2026 World Cup Schedule and Results
-Version: 0.5.0
+Version: 0.5.1
 Authors@R:
     person("Sharon", "Machlis", , "smachlis@gmail.com", role = c("aut", "cre"))
 Description: An R wrapper for the football-data.org v4 API that retrieves

NEWS.md

@@ -1,3 +1,16 @@
+# worldcup26 0.5.1
+
+* Bug fix: the publish workflow's schedule didn't match its documented
+  behavior. It defined only a single 12-minute cron, while the job's `if`
+  condition gated on an hourly cron string (`"0 0-6,15-23 * * *"`) that was
+  never registered. As a result the hourly fallback never matched, so when
+  `WORLDCUP26_LIVE` was `false` the site stopped rebuilding entirely instead of
+  refreshing once an hour. The workflow now registers two crons: an hourly tick
+  that always runs, and a 10-minute tick (`:10`-`:50`) that runs only when
+  `WORLDCUP26_LIVE` is `true`.
+
+  _[This update was written by Claude]_
+
 # worldcup26 0.5.0
 
 * The "By team" tab on the companion Quarto site now shows scores from the