CopilotKit v1.59.5: Make up for the return of "chat will reset itself"

CopilotKit releases v1.59.5. This is a targeted line of fixes - addressing a regression (ENT-658) introduced in v1.58 that affected multi-turn interaction continuity.

What’s the problem?

When threads are spawned by the SDK, during a round trip to the frontend tool, the chat is "visibly reset" and existing messages are lost. This interruption of context can be fatal for conversations that rely on multiple rounds of tool calls.

How to fix it

• threadId handling: Two independent causes of this problem were located and fixed in @copilotkit/react-core.
• Freeze Empty Singleton: Introduce frozen singletons such as EMPTY_HEADERS / EMPTY_PROPERTIES / EMPTY_AGENTS to eliminate the side effects of shared variable default values.
• Dependencies: license-verifier upgraded to ~0.4.2.

This regression was fixed in v1.59.1, and v1.59.5 continues this series of closures.

Who should upgrade?

Any project that uses front-end tools and observes message loss during the conversation should be directly upgraded to v1.59.5; after the upgrade, focus on returning to the multi-round process with front-end tools to confirm that the thread context is continuous. Since the changes involve react-core behavior, it is recommended to verify the existing integration in the test environment first. For complete changes, please refer to the official release notes.