fix(ci): use /actions/runs endpoint in deploy.yml wait-time steps #522

2026-06-07T04:30:37Z

guettlibot commented

2026-06-07 04:30:37 +00:00

(Migrated from codeberg.org)

Summary

The five "Print runner wait time" steps in deploy.yml were querying /actions/tasks but the Python code filtered on data.get('workflow_runs', []) — a key the tasks endpoint does not return. The correct endpoint is /actions/runs, whose JSON includes workflow_runs with the run_number and created_at fields.
Every deploy job was printing "Runner wait time: unknown (API lookup failed)". This fix makes the wait time report accurately.

Test plan

Trigger a workflow_dispatch on deploy.yml; verify each job prints a numeric wait time.
Confirm change-detection logic and deploy steps are unchanged.

Closes #521

🤖 Generated with Claude Code

## Summary - The five "Print runner wait time" steps in `deploy.yml` were querying `/actions/tasks` but the Python code filtered on `data.get('workflow_runs', [])` — a key the tasks endpoint does not return. The correct endpoint is `/actions/runs`, whose JSON includes `workflow_runs` with the `run_number` and `created_at` fields. - Every deploy job was printing "Runner wait time: unknown (API lookup failed)". This fix makes the wait time report accurately. ## Test plan - [ ] Trigger a `workflow_dispatch` on `deploy.yml`; verify each job prints a numeric wait time. - [ ] Confirm change-detection logic and deploy steps are unchanged. Closes #521 🤖 Generated with [Claude Code](https://claude.com/claude-code)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: guettli/sharedinbox#522