wangbo
e05922b0f4
实现本地三节点 K3s 同构环境、脱敏生产快照、Gemini 图片和多参考图视频协议模拟、统一验收报告及故障注入。\n\n新增 Worker 容量控制器、资源与连接预算、任务恢复保护，并将生产验收拆分为 validation 执行和人工 CAS 放量。\n\n验证包括 Go 全量测试、PostgreSQL HTTP 集成测试、go vet、OpenAPI、ShellCheck、前端检查、迁移及发布脚本测试。
36 lines
2.3 KiB
JSON
36 lines
2.3 KiB
JSON
{
|
|
"version": 1,
|
|
"migrations": {
|
|
"apps/api/migrations/0090_oidc_multi_tenant_identity.sql": {
|
|
"sha256": "d5e67a0f92f4fe5fb64f5caceef0dd4733dc65f921e309bf4b3288522f6b4876",
|
|
"allowedViolations": [
|
|
"destructive DROP operation",
|
|
"non-null column addition"
|
|
],
|
|
"reason": "The migration replaces two existing constraints and one index with expanded definitions. Production preflight confirmed six schema-v1 identity revisions, no OIDC sessions or revocation watermarks, and small affected relations; the non-null columns use constant defaults."
|
|
},
|
|
"apps/api/migrations/0093_worker_instance_capacity_limit.sql": {
|
|
"sha256": "4b6a39ef90e7032555739ccf0568bf7ae0bce23ef98c3bee9c2c8e3bfa13291e",
|
|
"allowedViolations": [
|
|
"non-null column addition"
|
|
],
|
|
"reason": "The table stores ephemeral Worker heartbeats and currently has only two production rows. PostgreSQL adds the integer column with a constant default, then the migration backfills each live row from its existing allocation so a rolling deployment cannot assign unsafe failover capacity."
|
|
},
|
|
"apps/api/migrations/0095_oidc_session_context_identity.sql": {
|
|
"sha256": "3e6d17b5b564047c4a77ef3e4cf4ed88caba375a34a33bc7ecfbd7c59d6ab479",
|
|
"allowedViolations": [
|
|
"destructive DROP operation",
|
|
"non-null column addition"
|
|
],
|
|
"reason": "The migration adds only nullable session identity columns, backfills bound sessions, and replaces one CHECK constraint without dropping data. Production preflight on 2026-07-31 found zero gateway_oidc_sessions rows and a 48 KiB relation, so the constraint validation and metadata lock are bounded; the non-null finding comes from the new CHECK expression rather than a NOT NULL column addition."
|
|
},
|
|
"apps/api/migrations/0096_worker_capacity_controller.sql": {
|
|
"sha256": "52c2c5f31eaa61b96508ae9b2c9fa164e0f1544184c55a1ba85f64b9aca442cb",
|
|
"allowedViolations": [
|
|
"destructive DROP operation"
|
|
],
|
|
"reason": "The migration replaces only the existing Worker status CHECK constraint so a rolling deployment can mark lost instances stale. It does not drop data, columns, tables, or indexes; the old and new binaries both continue to read active and draining rows safely."
|
|
}
|
|
}
|
|
}
|