chore(ai-reviews): bump ai-workflows pin to v3.1.4#36159
Conversation
v3.1.3 fixes silent "Codex Review failed" stickies: it handles the Responses-API response.incomplete case (reasoning consuming the whole output-token budget), raises the default budget to 8000, and retries once before giving up. ~43% of recent GPT-5.5 auto-reviews were affected. Validated e2e (before/after) on steve-quarterly-planning #105. Closes: #36158 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Claude finished @sfreudenthaler's task in 1m 0s —— View job Rollback Safety Analysis
Result: ✅ Safe to Roll Back The diff touches only two GitHub Actions workflow files:
There are no database migrations ( |
❌ Codex Review failed —
|
v3.1.4 adds clear human-facing outcome signaling on top of v3.1.3: the sticky header reflects the result (🤖 review /⚠️ truncated / ❌ no output / ⏱️ canceled), the job fails (red ✗ in checks) when no review is produced, and canceled/timed-out runs no longer leave a stuck "in progress" comment. ai-workflows#39. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Summary
Bumps the
dotCMS/ai-workflowspin in the AI review workflows from@v3.1.2to@v3.1.4(orchestrator + backend reviewer). Supersedes the intermediate v3.1.3 bump — v3.1.4 includes everything in v3.1.3 plus the outcome-signaling improvements, so we go straight to it.What's in v3.1.3 + v3.1.4
v3.1.3 — silent-failure fix (ai-workflows#38): ~43% of GPT-5.5 reviews were posting "❌ Codex Review failed — job failed before producing output." Root cause:
max_output_tokenscaps reasoning+answer combined, so medium-effort GPT-5.5 sometimes spent the whole budget reasoning and returnedincompletewith no text. Fix: budget 2048→8000, handleresponse.incomplete, retry once with a bigger budget + lighter reasoning.v3.1.4 — clear outcome signaling (ai-workflows#39):
🤖 Codex Review/⚠️ truncated/❌ no output/⏱️ canceled⏱️ Codex Review canceledinstead of leaving it stuck on🔄 in progressValidation
Closes: #36158