fix(report): keep the public table allowlist in sync with the longform appendix
The staging quality gate failed because database-local-business still listed the old pg_tables set after 20260905010000. Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -8454,3 +8454,19 @@
|
||||
- 复发自:BUG-546
|
||||
- 修复版本:`cd704a92`
|
||||
|
||||
## BUG-548 | 全量附录表未写入 public 表白名单,staging 质量门失败
|
||||
|
||||
- 状态:resolved
|
||||
- 首次发现:2026-09-05
|
||||
- 最近更新:2026-09-05
|
||||
- 影响面:Gitea `Independent Staging Quality Gate` / `validate`、`frontend/tests/database-local-business.test.ts`
|
||||
- 用户现象:`bab07187` 推 staging 后质量门失败,镜像未发布。用户看不到新的全量数据附录入口。
|
||||
- 触发条件:新增 `public.personal_report_longform_appendices` 后跑 `npm test --prefix frontend`。
|
||||
- 根因:`database-local-business` 把 `pg_tables` 的 public 表名单锁死。附录迁移已应用,名单仍缺 `personal_report_longform_appendices`,唯一失败项是 `not ok 949`。附录定向库测本身通过。
|
||||
- 修复:把该表按字母序写入白名单;断言 `20260905010000_personal_report_longform_appendices.sql` 已应用且未双写冻结的 `frontend/db/migrations`。
|
||||
- 验证:Gitea run 2416 日志仅此 1 fail;本机重跑 `database-local-business`。
|
||||
- 防复发:新增 `public` 表必须同步改这条 `string_agg(tablename)` 白名单,并写原值/新值/原因。`npm test` 会跑 `tests/*.test.ts`,含这条库测。
|
||||
- 相关记录:无
|
||||
- 复发自:无
|
||||
- 修复版本:本提交
|
||||
|
||||
|
||||
Reference in New Issue
Block a user