feat(ai-reviews): bump ai-workflows to v3.1.5 + switch auto-review to DeepSeek V3.2#36182
Conversation
v3.1.5 surfaces the actual failure reason on response.failed (was discarded — sticky just said "failed before producing output"). Now the ❌ sticky + job log show response.error (e.g. server_error), flag it as an AWS/mantle-side issue, and retry once on transient failures. Motivated by a real gpt-5.5 mantle outage. Closes: #36181 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Claude finished @sfreudenthaler's task in 45s —— View job Rollback Safety Analysis
Result: ✅ Safe To RollbackThe diff touches only two GitHub Actions workflow files:
None of the ROLLBACK_UNSAFE_CATEGORIES apply:
These are pure CI/CD workflow changes. Rolling back to the previous release leaves the application binary, database schema, Elasticsearch index, and all API contracts completely unchanged. Label |
❌ Codex Review — model service error —
|
gpt-5.5 is failing on Bedrock Mantle in both regions as of 2026-06-15
("Engine not found" — AWS-side; raised with our TAM). Switch the automatic
PR reviewer to deepseek.v3.2, which is healthy on bedrock-runtime and keeps
reviews running. deepseek.* routes to the bedrock-generic (Converse) executor;
no IAM change needed (BedrockInvokeReviewModels already allows Converse on
foundation-model/deepseek.*). Still a non-Claude reviewer, preserving the
model-diversity rationale. Renamed the job gpt-automatic-review ->
ai-automatic-review (model-agnostic) and dropped reasoning_effort (mantle-only).
Validated e2e on steve-quarterly-planning #108 (routed to bedrock-generic,
posted a real review).
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
🤖 Bedrock Review —
|
got confirmation from AWS TAM that gpt 5.5 was busted on their end (they just don't have a public place to find out). that's why it was working then stopped. v3.1.5 of ai-workflows fixes the problem that it was swallowing the error as well. |
Two changes to get automatic PR reviews working again and keep them legible:
1. Switch automatic reviewer GPT-5.5 → DeepSeek V3.2
openai.gpt-5.5is failing on Bedrock Mantle in both us-east-1 and us-east-2 as of 2026-06-15 (invalid_prompt: 404 Not Found: Engine not found— AWS-side; the alias and its-2026-04-23snapshot both 404 while still listed in/v1/models). Raised with our AWS TAM.deepseek.v3.2is healthy on bedrock-runtime (Converse) and is still a non-Claude reviewer, so it preserves the model-diversity rationale (Claude writes the code, a different family reviews it).deepseek.*routes to the existingbedrock-generic(Converse) executor — no IAM or ai-workflows change needed (BedrockInvokeReviewModelsalready allowsbedrock:Converseonfoundation-model/deepseek.*).gpt-automatic-review→ai-automatic-review(model-agnostic); droppedreasoning_effort(mantle-only).@claudeand the backend reviewer stay on Anthropic Claude.2. Bump pin v3.1.4 → v3.1.5
ai-workflows#40: surfaces the actual failure reason on
response.failed(e.g.server_error/Engine not found) in the sticky + job log instead of a generic "failed before producing output", and retries once on transient failures. This is exactly what made the gpt-5.5 outage diagnosable.Switch back to a mantle model by setting
model_idto anopenai.*id once AWS restores gpt-5.5.Closes: #36181