v1.2.1

A flaky test, fixed

The binaries are functionally identical to v1.2.0. No product code changed, and a deployment running v1.2.0 has no reason to reinstall. This tag exists so that the newest release is one whose full gate is green.

Two of the concurrency tests added in v1.2.0 tore down while a connection was still completing its Telegram handshake, and then counted the interrupted read as a proxy failure. A stream registers in admit, which runs before that handshake finishes, so waiting on the connection registry alone was not enough to know every stream was ready.

Locally the gap between the two is too small to hit; on a loaded CI runner it is wide enough that the Test job went red on the first run after the tests landed. The wait now covers both conditions, and the failure assertion moved ahead of teardown — where a failed handshake can only mean the proxy faulted, rather than that the test closed the socket underneath it.

The thing the tests were checking was correct throughout. They were wrong about when a stream is ready, not about what it does.

Everything from v1.2.0 still applies

Per-user client addresses on /stats behind track-client-ips (off by default), a tg:// link for every configured [[listener]] in the wire form that socket accepts, and release pages built from the tag annotation. See v1.2.0 for the detail.

Full Changelog: v1.2.0...v1.2.1