API client 0.7.18 no longer connects to Huly Cloud - "Data read, but end of buffer not reached"

[jeremiahsmithdev]

My integration using @hcengineering/api-client@0.7.18 (latest on npm) was working ~1 month ago but now fails with:

Connected to server: 0.7.353
[Bridge] Uncaught exception: Data read, but end of buffer not reached 112

This appears to be a msgpack protocol mismatch between the npm client (0.7.18) and the current Huly Cloud server (0.7.353).

Questions:

1. Was there a recent Huly Cloud upgrade that changed the protocol?
2. Are there compatible package versions that work with current Huly Cloud?
3. Could updated packages be published to npm or GitHub Packages?

Additional context:

• My .npmrc is configured for GitHub Packages but @hcengineering/core is not published there, blocking installation of newer api-client versions
• The connection establishes successfully and negotiates the session, but fails on the first data response
• Using token-based authentication with workspace parameter

Environment:

• @hcengineering/api-client: 0.7.18 (latest on npmjs.org)
• Huly Cloud server reports: 0.7.353
• Node.js 20.x

[huly-github-staging]

Connected to Huly®: UBERF-15381

[ArtyomSavchenko]

Hello @jeremiahsmithdev
I assume api-client was not updated.
We will try to fix this in the coming days.