[szanata]

Summary

• Fixed release v0.16 docs according to findings on chore(release): v0.16.0 #472

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
outputai	🟢 Ready	View Preview	Nov 2, 2026, 2:49 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[claude]

Nice-to-have (Documentation): :latest fixes the drift but un-pins a production deploy. ops/publish_api.sh also pushes :0 and :0.16 aliases — a pinned tag (or a note that latest floats) is safer guidance given 0.x minors carry breaking changes.

[github-actions]

PR review

Verdict

✅ PASS

Findings

1. Nice-to-have (Documentation): The Railway/Render guides now tell self-hosters to deploy docker.io/outputai/api:latest (railway.mdx:47, render.mdx:99). That removes the staleness but un-pins a production deployment: latest floats across 0.x minors that carry documented breaking changes, and the paired worker stays pinned to a specific @outputai/core (fixed version group). ops/publish_api.sh also pushes :0 and :0.16 aliases — pinning the current release, or adding a one-line note that latest floats, would be safer guidance.

2. Nice-to-have (Compatibility): The failure-cause change is user-observable in API error responses (api/src/clients/temporal/workflow_result.js flattens the .cause chain), but the migration guide covers it with only a "What changed" bullet and a checklist line — no before/after shape like the sendHttpRequest() section has. A two-line example of the old vs. new nesting would make it actionable for anyone parsing error cause.

Categories

• Design: ✅ PASS
• Quality: ✅ PASS
• Correctness: ✅ PASS
• Documentation: ✅ PASS
• Changeset: ✅ PASS
• Tests: ✅ PASS
• Security: ✅ PASS
• Compatibility: ✅ PASS