Jinwoo Hong 1957437005 fix(relay): stop admin routes reporting a stalled database as 404 or 409 (#21264) ...

Every admin handler collapsed a thrown error into one status, so a two-second
pool connect timeout answered POST /v1/admin/cell-status with 404. The rollout
tooling never retries a 4xx, by design, so the wave failed on a database that
was briefly out of reach and recovered on its own.

Transient database failures now answer 503 with Retry-After, the shape the
public routes and the region catalog already use. Every other error keeps the
route's existing 404 or 409 mapping.

2026-09-17 14:02:06 -04:00

..

src

fix(relay): stop admin routes reporting a stalled database as 404 or 409 (#21264)

2026-09-17 14:02:06 -04:00

Dockerfile

feat(cloud): native push gateway and dedicated infrastructure (1/3) (#19912)

2026-09-10 17:59:46 -04:00

package.json

fix(deps): update vulnerable dependencies without new overrides

2026-09-16 20:36:24 -07:00

tsconfig.build.json

feat(relay): correct regional placement only when the source is idle (#20105)

2026-09-11 14:25:10 -04:00

tsconfig.json

chore(cloud): add the relay fence broker, ops console, Terraform root, scripts, and 24 cloud-* workflows (#18413)

2026-09-03 06:55:14 -04:00

vitest.config.ts

chore(cloud): add the relay fence broker, ops console, Terraform root, scripts, and 24 cloud-* workflows (#18413)

2026-09-03 06:55:14 -04:00