Files
copilotkit__copilotkit/showcase/scripts/fail-baseline.json
Alem Tuzlak c0eaa00b73 chore(showcase-scripts): bump validatePinsFailCount to 112 for voice demo
The voice demo adds two new framework deps (@copilotkit/voice, openai)
to showcase/packages/langgraph-python. The Dojo example doesn't pin
either, so validate-pins emits [FAIL] "is not an exact pin in showcase"
for each. Both use the same non-exact spec style as the already-baselined
@copilotkit/react-core / @copilotkit/runtime entries (next-channel dist
tag + caret range). Bump the drift baseline by 2 so CI accepts the new
deps without lowering the overall pin discipline.
2026-04-23 22:31:10 +02:00

7 lines
1005 B
JSON

{
"_comment": "Drift ratchet baseline for showcase_validate.yml. `validatePinsFailCount` holds the last-known FAIL count; `validatePinsFailHash` is a SHA-256 of the sorted, deduplicated `[FAIL] ...` lines from validate-pins.ts. CI compares BOTH: if the count changes, it tells you to ratchet (up rejected, down instructed). If the count is equal but the hash differs, the FAIL *set* has drifted (one item fixed, another regressed) and CI fails with a diff. Never raise the count without an explicit review + sign-off. `baselineDemoCount` is the per-package e2e-spec-count floor (single source of truth consumed by both the workflow and validate-parity.ts). NOTE: validate-parity.ts `BASELINE_DEMO_COUNT` default must match `baselineDemoCount` here; keep them in sync. See .github/workflows/showcase_validate.yml 'Run validate-pins (ratchet)' step.",
"validatePinsFailCount": 112,
"validatePinsFailHash": "3fd149f706e3fa1c1e852d4c790f0d6de7d725353246ba8c4e82f3408a662de4",
"baselineDemoCount": 9
}