Skip to content

chore(ai-reviews): bump ai-workflows pin to v3.1.4#36159

Merged
sfreudenthaler merged 2 commits into
mainfrom
chore/ai-workflows-v313
Jun 13, 2026
Merged

chore(ai-reviews): bump ai-workflows pin to v3.1.4#36159
sfreudenthaler merged 2 commits into
mainfrom
chore/ai-workflows-v313

Conversation

@sfreudenthaler

@sfreudenthaler sfreudenthaler commented Jun 13, 2026

Copy link
Copy Markdown
Member

Summary

Bumps the dotCMS/ai-workflows pin in the AI review workflows from @v3.1.2 to @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_tokens caps reasoning+answer combined, so medium-effort GPT-5.5 sometimes spent the whole budget reasoning and returned incomplete with no text. Fix: budget 2048→8000, handle response.incomplete, retry once with a bigger budget + lighter reasoning.

v3.1.4 — clear outcome signaling (ai-workflows#39):

  • Sticky header reflects the outcome: 🤖 Codex Review / ⚠️ truncated / ❌ no output / ⏱️ canceled
  • The job fails (red ✗ in checks) when no review is produced — surfaces the outcome without gating merges (advisory review)
  • Canceled / timed-out runs rewrite the sticky to ⏱️ Codex Review canceled instead of leaving it stuck on 🔄 in progress

Validation

Closes: #36158

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>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@claude

claude Bot commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Claude finished @sfreudenthaler's task in 1m 0s —— View job


Rollback Safety Analysis

  • Gather context: read PR diff and rollback-unsafe categories
  • Analyze diff against all unsafe categories
  • Apply label: AI: Safe To Rollback

Result: ✅ Safe to Roll Back

The diff touches only two GitHub Actions workflow files:

  • .github/workflows/ai_claude-backend-reviewer.yml — bumps dotCMS/ai-workflows pin from @v3.1.2@v3.1.4
  • .github/workflows/ai_claude-orchestrator.yml — same pin bump on three uses: lines

There are no database migrations (runonce tasks), no Elasticsearch mapping changes, no data model changes, no REST/GraphQL API contract changes, no OSGi interface changes, no VTL viewtool changes, and no binary storage modifications. The changes are pure CI/CD configuration — they affect only how GitHub Actions workflows call an external reusable workflow. None of the unsafe categories (C-1 through C-4, H-1 through H-8, M-1 through M-4) apply.

@github-actions

github-actions Bot commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

❌ Codex Review failed — openai.gpt-5.5

The review job failed before producing output. See the run for details.

Run: #27470981829

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>
@sfreudenthaler sfreudenthaler changed the title chore(ai-reviews): bump ai-workflows pin to v3.1.3 chore(ai-reviews): bump ai-workflows pin to v3.1.4 Jun 13, 2026
@sfreudenthaler sfreudenthaler enabled auto-merge June 13, 2026 15:46
@sfreudenthaler sfreudenthaler added this pull request to the merge queue Jun 13, 2026
Merged via the queue into main with commit fcfe940 Jun 13, 2026
37 of 38 checks passed
@sfreudenthaler sfreudenthaler deleted the chore/ai-workflows-v313 branch June 13, 2026 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AI: Safe To Rollback Area : CI/CD PR changes GitHub Actions/workflows

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

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

2 participants