Request: tag a new release to include notification ordering fixes (#5, #8)

[strofimovsky-trulioo]

Context

Several important bug fixes have landed on main since v0.6.3 (Nov 2025):

• Fix race condition where Prompt() returns before SessionUpdate handlers complete #5 — Fix race condition where Prompt() returns before SessionUpdate handlers complete (merged Dec 5, 2025)
• fix: messages out of order #8 — Serialize notification processing to maintain message order (merged Feb 24, 2026)

These fix a class of race conditions where session/update notification handlers run after Prompt() has already returned, causing downstream consumers to see empty or garbled results.

Impact

Multiple downstream projects pinned to v0.6.3 are hitting these issues:

• Race condition: notifications processed out of order due to goroutine-per-message #20 — Race condition report by @jcfs (still open)
• Connection.receive dispatches notifications via goroutines, breaking SessionUpdate ordering #27 — SessionUpdate ordering report by @salekseev (closed as fixed on main)

In our case, ~86% of ACP review jobs return empty output to the caller while the log file (written by the same handler goroutine, but after Prompt() returns) contains the full content. The root cause is exactly the race fixed by #5 and #8.

Request

Would it be possible to cut a new tagged release? We're currently considering pinning to a main commit, but a proper semver tag would be much preferred for dependency management.

I understand #17 was a significant change (unstable ACP schema support). If that needs stabilization time before tagging, a heads-up on expected timing would be very helpful so downstream consumers can plan accordingly.

Thanks for maintaining this SDK — the fixes themselves are solid, they just need a release vehicle.

[martinsotirov]

Ah, good old vibecoded abandonware where PRs are unwelcome :(

[Cali0707]

We're currently considering pinning to a main commit

+1 - we are considering this as well

Would definitely prefer to have a semver tag to pin to

[ThomasK33]

Hey, sorry for the delay, created two new releases, one with the v0.10.8 and a new one with the v0.11.7 one.