mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
Jordan Ritter
2769cff509
llamaindex, agno, and claude-sdk-python emit AG-UI REASONING_MESSAGE_* events but pinned @ag-ui/client ^0.0.43, whose @ag-ui/core discriminated union lacks the REASONING_MESSAGE_* variants — the frontend threw invalid_union_discriminator and the reasoning demo broke. Pin all three to exact 0.0.48 (matching the claude-sdk-typescript fix in #5323), regenerate their lockfiles so @ag-ui/core resolves to 0.0.48 with zero 0.0.43 nodes, and ratchet the validate-pins drift baseline down from 60 to 57 to reflect the now-exact pins. Verified locally on the built-image showcase rig: D5 green and the D6 reasoning-display probe passes for all three backends with zero invalid_union_discriminator.
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": 57,
|
|
"validatePinsFailHash": "e5b9fb5081edcd3dc9d279e9dc32bb5850ba7abd9b367140e54f6b44247f9ce0",
|
|
"baselineDemoCount": 9
|
|
}
|