Commit e231b1e
fix(lanes): the deployment-basis propagation had no schedule (#1606)
backfill-deployment writes `deployment.basis` inside curate-projects.yml every
Tuesday 07:30 UTC. The pass that turns that into a STATUS basis had
workflow_dispatch and nothing else, so a newly stamped row waited on somebody
remembering to press a button. Its last run before today was 2026-09-07 —
eight days and one full producer cycle earlier.
Now it runs an hour behind the producer, same day, so each week's deployment
writes are consumed the moment they land. A scheduled run carries no `inputs`,
so the step needed curate-projects.yml's `github.event_name == 'schedule'`
shape or the cron would have dry-run forever.
Verified first rather than assumed: dispatched a dry run today and it would
have written 0 — 86 rows unchanged, 1 could-not-propagate (bondhive, no
sourceUrl, no receipt, no asset payments). Nothing is waiting right now. The
point is that nothing would have noticed when something was.
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>1 parent 437597e commit e231b1e
1 file changed
Lines changed: 16 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
20 | 20 | | |
21 | 21 | | |
22 | 22 | | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
23 | 36 | | |
24 | 37 | | |
25 | 38 | | |
| |||
47 | 60 | | |
48 | 61 | | |
49 | 62 | | |
50 | | - | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
0 commit comments