mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
Alem Tuzlak
9df97ee23b
The previous commit fixed the universal ADK loop + agent renames + A2UI shape, which changed the pin-status of ~half of the google-adk demos in the validate-pins matrix. Total FAIL count is unchanged at 95 (no regression elsewhere), but the SET of failing tuples drifted, which the ratchet correctly caught. Updates validatePinsFailHash to the new sorted-failing-set SHA from the CI run (62e06e1e...0b04d5e0). No baseline count change — `_comment` explicitly forbids raising the count without sign-off.
7 lines
1004 B
JSON
7 lines
1004 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": 95,
|
|
"validatePinsFailHash": "62e06e1eb88cc08cdb2438e191a285fb7e549512857287898a32eb640b04d5e0",
|
|
"baselineDemoCount": 9
|
|
}
|