Repository navigation
v0.1.4 — Render deploys and provider reliability
What’s new
Deployment
- A documented Render deployment path:
render.yamlfor api, worker, Postgres and Key Value, with a walkthrough covering bootstrap andPUBLIC_BASE_URL. Object storage stays external (Cloudflare R2 or any S3 endpoint), since Render has no S3-compatible service. - The OIDC redirect URI is built from
public_base_url, so per-tenant login works behind a real hostname.
Provider failures are retried, not blamed on the agent
- An aggregator that loses its upstream mid-generation reports it inside an HTTP 200 (
finish_reason: "error"). That now retries like any 429/5xx, instead of failing the job. A model that genuinely misbehaved still fails, since retrying that only spends the budget again. - A model that refuses forced tool choice falls back to asking for the schema in the prompt, so an agent with an output schema is no longer unusable on that model.
- A job whose worker was shut down mid-run is requeued rather than marked failed.
- An eval run the provider never let finish ends
erroredwith no pass rate, so a hiccup cannot become the baseline a real regression is measured against, or make a pending memory version look like it failed its gate.
Cost accounting says what it doesn’t know
- OpenRouter's real per-generation charge is taken from OpenRouter, since no static table can price an aggregator.
- A model with no price records the gap instead of a silent zero, which would leave spending limits inert.
- A cost missing a generation's record is flagged (
cost_incomplete) rather than reported as though it were exact.
Observability and fixes
- Tool calls are recorded in the job trail, so a finished job can answer whether the model actually read its source.
- Store listings come back in the coordinate system the tools accept.
- A model row's provider must match its model string, caught at registration instead of at job time.
- The create-agent form publishes a complete first version.
Storage images
- MinIO archived
minio/minioand removed it from Docker Hub. CI and compose now usecgr.dev/chainguard/minio, pinned by digest: the same server, built from a fork that carries the CVE fixes, rebuilt daily. Langfuse moved to the same image (langfuse/langfuse#10488).
Upgrade
No migrations in this release.
Compose users get a new storage image; docker compose pull before up. The image is pinned by digest, so updating it is deliberate. Deployments that already use external S3 (R2 on Render) are unaffected.
Verification
314 tests passed.