dotCMS / dotCMS/core

chore(ai-reviews): bump ai-workflows pin to v3.1.4 (silent-failure fix + clear outcome signaling)

Open Beginner friendly
#36,158 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

stale Team : Enablement
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Summary

Bump the dotCMS/ai-workflows pin in the AI review workflows from @v3.1.2 to @v3.1.3.

Why

~43% of recent GPT-5.5 automatic reviews were posting "❌ Codex Review failed — job failed before producing output" and giving the PR no review. Root cause (fixed in ai-workflows#38, released as v3.1.3): on the Responses API, max_output_tokens caps the combined reasoning + answer tokens, so at reasoning_effort: medium GPT-5.5 sometimes spent the whole 2048 budget reasoning and returned status=incomplete with no visible text — which the executor treated as a hard failure.

v3.1.3 raises the default budget to 8000, captures the incomplete terminal event, retries once with a larger budget + lighter reasoning, and posts a clear diagnostic instead of a generic failure.

Validated e2e (before/after) on dotCMS/steve-quarterly-planning #105.

Changes

  • ai_claude-orchestrator.yml: @v3.1.2@v3.1.3 (both jobs)
  • ai_claude-backend-reviewer.yml: @v3.1.2@v3.1.3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with ai_claude-orchestrator.yml and ai_claude-backend-reviewer.yml, locating the referenced dotCMS/ai-workflows pins in both orchestrator jobs and the backend reviewer. Resolve the version discrepancy between the title's v3.1.4 and the body and changes' v3.1.3, then verify both workflow files use the intended release.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
76/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.