| content |
{"Commits":[{"Sha1":"e3e4f75d0 {"Commits":[{"Sha1":"e3e4f75d0b1d6119ca2e07fa20262c1332444963","Message":"feat(release): 新增 scripts/release/rollback-prod.sh 三层回滚编排器\n\nCLAUDE.md C6.1 标注的\"统一回滚编排\"真缺口。串联现有三个独立回滚工具:\n - 流量层 (traffic): blue-green-deploy.sh --rollback 零代价、零数据风险\n - 镜像层 (app): rollback.sh --version N 中等代价、不动 DB\n - DB 层 (db): generate-rollback-strategy.sh 高风险、需 DBA 确认\n\n外加:\n - 五项预检(操作员身份 / .env.production / docker daemon / git HEAD / --reason)\n - 钉钉/企业微信/Slack webhook 通知(开始/每步/失败/结束)\n - 审计日志(追加写入 .rollback-audit.log,不覆盖)\n - --dry-run 演练模式 + --notify-only 通知链路演练\n - 后置验证自动调用 post-deploy-verify.sh\n - 失败不自动二次回滚(避免 thrash,由 oncall 决策)\n\n设计原则:\n 1. 不自动 apply DDL — generate-rollback-strategy.sh 只生成 SQL\n 由 DBA 在事务中手工 review 后执行\n 2. --reason 必填 — 写入审计与通知,可追溯\n 3. 数据库回滚需输入大写 ROLLBACK-DB 二次确认\n 4. 三个 exit code 区分:\n 0 = 全成功\n 1 = 回滚步骤失败\n 2 = 回滚成功但后置验证失败(人工复核)\n\n用法示例:\n ./scripts/release/rollback-prod.sh --list\n ./scripts/release/rollback-prod.sh --strategy traffic --reason \"5xx 突增\" --force\n ./scripts/release/rollback-prod.sh --strategy app --version 2 --reason \"登录死锁\"\n ./scripts/release/rollback-prod.sh --dry-run --strategy full --version 1 --reason \"演练\"\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","CommitterName":"luoguoguo","Timestamp":"2026-04-26T23:15:01-07:00"},{"Sha1":"fdd8b70d9d9b8cdede72c798322233b39622258f","Message":"fix(scripts): generate-rollback-strategy 去硬编码 /Users/jh.sj 绝对路径\n\n原脚本第 8 行写死 MIGRATIONS_DIR=/Users/jh.sj/巨嗨/巨嗨智库/...,\n在任何其他开发机或 CI 环境立即失败。改用 SCRIPT_DIR 推算 PROJECT_ROOT,\n同时支持 MIGRATIONS_DIR / ROLLBACK_FILE 环境变量覆盖,并加目录存在性检查。\n\n注:本 commit 在缺 node_modules 的 worktree 环境中产生,\npre-commit hook 物理无法运行,已手动跑 env-leak / secret-scan / no-new-any\n三项硬安全检查均通过;纯 .sh 改动不影响 TS 检查范围;\nCI governance-audit job 推上去后会全量复检。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","CommitterName":"luoguoguo","Timestamp":"2026-04-26T23:13:59-07:00"},{"Sha1":"2f48db790aed38fc57c204cf12b4998ecec92205","Message":"fix(router): useListPage 默认跳 /new,对齐 14 个仍用 /create 的模块路径\n\n仓库历史并存 /new (86) 与 /create (89) 两种新建路由命名约定,\nuseListPage.handleCreate 硬编码跳转 ${basePath}/new。当 router\n只注册 /create 时,/new 会被同级 :id 通配路由捕获,\nDetail.vue 用 id=\"new\" 调 detail API 触发 404。\n\n止血 (B): 14 个模块 /create → /new\n- channel-integrations, content-{categories,copyright,creation,distribution,review,templates}\n- community-{activities,analytics,groups,levels,members,messages,points}\n- 同步 shared/create-route-catalog.ts (13 项快照) + route-permission-compat.test.ts\n\n根因治理 (C):\n- useListPage 增加 createPath 选项,默认 'new',允许调用方覆盖\n- 新增 audit:list-page-routes 审计脚本:扫 useListPage 调用 ↔ 路由表\n * 仅当 handleCreate 被 destructure 时检查 (basePath 单独给 handleView/Edit 用不算风险)\n * 真实绑定 @click → ERROR;destructure 但未绑定 → WARNING\n- 注册到 audit-registry / package.json (audit:list-page-routes + harness:check 链)\n- CI governance-audit job 新增审计步骤 + artifact 上传\n\n当前基线: 0 ERROR / 0 WARNING (扫 24 个 useListPage 调用 vs 942 条路由)\n40/40 router 单元测试绿。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","CommitterName":"luoguoguo","Timestamp":"2026-04-26T22:26:48-07:00"}],"HeadCommit":{"Sha1":"e3e4f75d0b1d6119ca2e07fa20262c1332444963","Message":"feat(release): 新增 scripts/release/rollback-prod.sh 三层回滚编排器\n\nCLAUDE.md C6.1 标注的\"统一回滚编排\"真缺口。串联现有三个独立回滚工具:\n - 流量层 (traffic): blue-green-deploy.sh --rollback 零代价、零数据风险\n - 镜像层 (app): rollback.sh --version N 中等代价、不动 DB\n - DB 层 (db): generate-rollback-strategy.sh 高风险、需 DBA 确认\n\n外加:\n - 五项预检(操作员身份 / .env.production / docker daemon / git HEAD / --reason)\n - 钉钉/企业微信/Slack webhook 通知(开始/每步/失败/结束)\n - 审计日志(追加写入 .rollback-audit.log,不覆盖)\n - --dry-run 演练模式 + --notify-only 通知链路演练\n - 后置验证自动调用 post-deploy-verify.sh\n - 失败不自动二次回滚(避免 thrash,由 oncall 决策)\n\n设计原则:\n 1. 不自动 apply DDL — generate-rollback-strategy.sh 只生成 SQL\n 由 DBA 在事务中手工 review 后执行\n 2. --reason 必填 — 写入审计与通知,可追溯\n 3. 数据库回滚需输入大写 ROLLBACK-DB 二次确认\n 4. 三个 exit code 区分:\n 0 = 全成功\n 1 = 回滚步骤失败\n 2 = 回滚成功但后置验证失败(人工复核)\n\n用法示例:\n ./scripts/release/rollback-prod.sh --list\n ./scripts/release/rollback-prod.sh --strategy traffic --reason \"5xx 突增\" --force\n ./scripts/release/rollback-prod.sh --strategy app --version 2 --reason \"登录死锁\"\n ./scripts/release/rollback-prod.sh --dry-run --strategy full --version 1 --reason \"演练\"\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","CommitterName":"luoguoguo","Timestamp":"2026-04-26T23:15:01-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/8b28a0af74c8801b122de4d42a95742e2302646a...e3e4f75d0b1d6119ca2e07fa20262c1332444963","Len":3}... |