release: promote develop→main — ship #11413 restores + migrate-runner fix to prod - #11450
Conversation
Co-authored-by: Shaw <shawgotbags@gmail.com>
Squash merge #11442. Local evidence: app voice wildcard Playwright lane passed 14/14; repo verify blocked by existing type-safety ratchet baseline documented in PR.
Fixes #11378. Adds smithers to the benchmark trajectory diff viewer, adds step-through playback, and commits viewer-server tests plus desktop/mobile evidence.
Restores the deferred #11271 CI orchestration tail for #11413: test/scenario/Kokoro workflows, post-merge real-live accounting, manifest ratchets, UI fixture runner CI wiring, and evidence.\n\nLocal verification is documented in .github/issue-evidence/11413-ci-orchestration-tail.md. Root verify still fails on the pre-existing current-develop type-safety ratchet drift.
Co-authored-by: Shaw <shawgotbags@gmail.com>
…rod deploys when hosted queue is jammed (#11449) The migrate-db gate (every deploy job `needs` it) was hardcoded runs-on: ubuntu-latest. When the org-wide GitHub-hosted queue backs up for hours (the recurring zombie-freeze), migrate-db never gets a runner and ALL prod deploys stall — even though the self-hosted hetzner-robot pool is idle (it runs the deploy jobs fine). Today the develop→main promote (#11434, money-gate restore) sat queued 1.5h+ on this exact gate while prod stayed stale. Make it configurable via CLOUD_CF_MIGRATE_RUNNER_JSON (defaults to ["ubuntu-latest"], preserving the deliberate hosted default). Ops can fail migrations over to the robot pool when hosted is jammed. Migrate is a light `bun install` + `db:cloud:migrate`, not the heavy working-tree materialization that motivated keeping deploys off the self-hosted fleet, so the robots handle it safely. actionlint clean.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
LifeOps Benchmark —
|
LifeOps Benchmark —
|
2 participants
Re-promote after the migrate-db runner fix (#11449). The previous promote (#11434, 4e3fa8e) is merged to main but its deploy stalled 1.5h+ on the hosted-queue migrate-db gate. This promote's deploy will read the FIXED workflow (migrate-db on the robot pool via CLOUD_CF_MIGRATE_RUNNER_JSON, now set) → migrations run instantly → the #11413 money-gate + runtime restores finally reach prod.
Ships develop (all #11413 restores + #11449 migrate fix + everything merged since) to production. Migrations idempotent (already applied). — nubs-cloud [cloud-frontdoor]