chore(clients/dotnet): bump Contracts + Client 0.3.0 -> 0.4.0 for publish (#227)
ci / nightly-windev (push) Has been skipped
ci / windows-x86 (push) Failing after 1m34s
ci / java (push) Failing after 2m33s
ci / portable (push) Failing after 3m39s

Ships the opt-in stream-attached acknowledgement (afd504d5) so OtOpcUa
can adopt it (lmxopcua#877). Published to the Gitea feed 2026-11-12.
This commit is contained in:
Joseph Doherty
2026-11-12 07:32:01 -05:00
parent afd504d5ae
commit 447070a532
4 changed files with 12 additions and 3 deletions
+9
View File
@@ -137,6 +137,15 @@ alarm ack. The minor bump marks a new wire field. The Python, Rust, Java and
Go clients were not republished in that release, and their manifests were
left alone.
On 2026-11-12 (#227) the .NET pair alone moved to **0.4.0**: `nuget`
`ZB.MOM.WW.MxGateway.Contracts` **0.4.0** and `ZB.MOM.WW.MxGateway.Client`
**0.4.0**. The release carries the additive opt-in stream-attached
acknowledgement from `afd504d5` (`StreamEventsRequest.emit_stream_attached`,
`MxEvent.stream_attached`, capability `stream-events-attached-ack`) and the
client's `OpenEventStreamAsync` awaitable, so OtOpcUa can close the
subscribe-before-attach race (lmxopcua#877). The Python, Rust, Java and Go
clients were not republished, and their manifests were left alone.
**The published pypi `0.2.0` artifact has a broken `connect()` (CLI-46).**
Its `connect()` built the `grpc.aio` channel inside `asyncio.to_thread`, and
a `grpc.aio` channel binds to the event loop current on the *constructing*