mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
Benjamin Taylor
b8c0ce99ed
Our packages pinned @ag-ui/{core,client,encoder,proto} exactly at 0.0.57.
@ag-ui/mastra@1.1.2 imports `tokenUsageFromAiSdkUsage`, which only exists
from @ag-ui/core@0.0.58, while declaring a loose `>=0.0.44` peer. Any app
that pins core to whatever our runtime pins therefore installs cleanly and
then fails at bundle time on a missing export.
0.0.58 is additive over 0.0.57 (TokenUsage schema + helpers, optional
`usage` field) plus one input-widening: TOOL_CALL_START.parentMessageId now
accepts null and coerces it to undefined instead of rejecting it.
That widening makes two channels-core negative-control tests stale. They
asserted that a null parentMessageId aborts a run when sanitizeAgentEventStream
is not applied -- the upstream bug the sanitizer works around. Core 0.0.58
fixes it upstream, so those runs now succeed; the tests are updated to assert
the new behavior. The sanitizer is kept: it normalizes null to "" whereas core
coerces to undefined, and it is public API.
Scope note: showcase/integrations and the examples that pin published
@copilotkit versions are deliberately NOT bumped. They have no @ag-ui
override, so raising only their direct pin would hoist 0.0.58 at the root
while @copilotkit/* keep nested 0.0.57 copies -- turning one coherent copy
into a split. They pick up 0.0.58 when they bump their @copilotkit pins.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>