From 7e594054e441dab476906d43f8ff494a06a409ec Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Wed, 12 Aug 2026 02:44:28 -0400 Subject: [PATCH] build(deps): adopt ZB.MOM.WW.Auth 0.2.0 and MxGateway client/contracts 0.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Brings the two shared-library families that had fallen behind the Gitea feed up to latest; the other 20 ZB.MOM.WW.* packages were already at feed-latest. Auth 0.1.5 -> 0.2.0 is LDAP failover only: a new LdapOptions.FallbackServers list, an endpoint walk with sticky preference in LdapAuthService, and per-hop warning logs. Purely additive — with FallbackServers empty (the committed default everywhere) the walk collapses to exactly one attempt, so behaviour is unchanged until someone opts in. Nothing in Auth.ApiKeys changed, so there is no key-store schema migration to sequence. MxGateway 0.1.1 -> 0.2.0 matters more than the version gap suggests: upstream records that four clients "had drifted onto the already-published 0.1.2/0.1.1 while their APIs kept changing underneath", so 0.1.1 was a stale label rather than a stable point. Real deltas since: status/HRESULT reply validation made conformant across clients (CLI-37/38), the ReplayGap reconnect sentinel surfaced as a typed signal (CLI-15), and typed single-item command parity (CLI-04/30). The one change touching the write path — correlating OnWriteComplete onto plain Write/Write2 replies — is server-side. Its proto diff is comment-only and the behaviour lives in the Worker, so ScadaBridge gains the correlated statuses when the gateway server is upgraded, not from this bump. No wire-contract break. Verified: restore and full solution build clean (0 warnings, 0 errors); all 22 shared packages resolve to a single version each across all 57 projects, with no split resolution. Security 181/181, InboundAPI 269/269, DataConnectionLayer 277/277 — the three suites that consume these packages directly. Full-sweep residue is pre-existing and unrelated, confirmed 3/3 green in isolation for the first two: - GrpcCentralTransportTests.DeadlineExceeded_IsNotRetriedOnThePeer — a saturated TestServer can fail to START the call, which IsConnectFailure correctly treats as provably-unsent and fails over; the harness cannot guarantee the DeadlineExceeded it means to exercise. - AuditLogOptionsBindingTests.Filter_PicksUp_NewBodyRedactor_OnConfigReload — not a reload race (the test is synchronous); it trips the 100 ms compile budget in AuditRegexCache, which fails OPEN. Filed as its own issue. - CentralUI Playwright 159/173 — login failures against the running rig, which was built from the pre-bump image and so cannot be affected by this change: 20 from the known SEC-36 GLAuth password rotation, 136 cascading from the login throttle. The rig still runs the previous libraries; it needs a docker/deploy.sh rebuild to pick these up. --- Directory.Packages.props | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Directory.Packages.props b/Directory.Packages.props index 67c3c9e0..8a7bc3eb 100644 --- a/Directory.Packages.props +++ b/Directory.Packages.props @@ -95,13 +95,13 @@ - - + + - - - - + + + +