You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Deploy #4172, whose release commit started no deploy run #4189
#4172 merged on 4 November at 10:14 UTC, and the versioning job pushed its release commit, 4169ac07d ("Update PolicyEngine API"), at 10:19 UTC. No workflow run started for that commit: GitHub was returning server errors at the time. Production deploys only from the Push run of a release commit, so #4172's retry_after_seconds is on master but not in production.
push.yml runs only on a push to master, so the lost run can't be started again, and master's ruleset refuses a direct push. A pull request that adds only a changelog fragment gets a new release commit when it merges, and that commit's Push run deploys everything on master, #4172 included.
Activity
anth-volk commentedon Nov 4, 2026
Not needed: #4177 merged at 15:28 UTC, and the Push run of its release commit
f06be4b31deploys everything onmaster, #4172 included.