Rollback on Mengboy 技术笔记

OpenAI Responses + GitHub Actions PR Risk Gate: Automated Evals, Tiered Blocking, and One-Click Rollback

Mon, 16 Mar 2026 01:08:00 +0000

You don’t need an AI reviewer that “sounds smart.” You need a gate that stops risky PRs before they hit main.

This post shows a production-ready minimum setup: OpenAI Responses generates structured risk output, GitHub Actions enforces tiered policies, and critical failures can trigger a one-click rollback.

OpenAI Responses + GitHub Actions 的 PR 风险闸门：自动评测、分级阻断与一键回滚

Mon, 16 Mar 2026 01:08:00 +0000

你不需要一个“会聊天”的 AI 审查器，你需要一个能阻断坏改动进主干的风险闸门。

这篇给一套可上线的最小方案：OpenAI Responses 负责生成结构化审查结论，GitHub Actions 负责分级阻断，发现高风险时自动回滚到安全提交。

OpenAI Responses Structured Outputs + Go：Schema 演进、坏样本兜底与灰度回滚

Wed, 11 Mar 2026 01:08:00 +0000

Structured Outputs 最容易翻车的地方，不是“模型不听话”，而是你把 schema 当成了永远不变的圣旨。

线上一旦进入版本演进期，最常见的事故就是：字段新增后老消费端崩、枚举值扩展后校验误杀、坏样本把整条链路拖死，最后只能半夜回滚，像在给自己写惊悚片。

OpenAI Responses Structured Outputs with Go: Schema Evolution, Bad-Case Fallbacks, and Gradual Rollback

Wed, 11 Mar 2026 01:08:00 +0000

The hardest part of Structured Outputs is not getting JSON once. It is surviving schema changes without turning production into a small fire with excellent logs and terrible business results.

Once a Go service starts evolving prompts and response contracts, the usual failure modes show up fast: a new required field breaks older consumers, an enum expands and strict validation kills valid requests, or one bad sample drags the whole chain into retries and rollback panic.