From 253939cd5d06ddecf64ee0acdb4a10d6bb867439 Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Mon, 28 Sep 2026 21:31:05 -0400 Subject: [PATCH] docs(site-secrets): Secrets 0.6.3 is published (not consumed by ScadaBridge) --- .../2026-09-28-site-secrets-artifact-deploy-design.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/plans/2026-09-28-site-secrets-artifact-deploy-design.md b/docs/plans/2026-09-28-site-secrets-artifact-deploy-design.md index c2a3798c..2ce7ad93 100644 --- a/docs/plans/2026-09-28-site-secrets-artifact-deploy-design.md +++ b/docs/plans/2026-09-28-site-secrets-artifact-deploy-design.md @@ -215,11 +215,10 @@ accurate as the spec: Grpc mode) — without that fix a central's boot-time `${secret:}` tokens and its running `ISecretResolver` could resolve a token differently. - **`ZB.MOM.WW.Secrets` 0.6.3 (hub sweep logging, §3.7's third bullet — `EventId`s 4/5/6, - `ISecretsHubSyncStatus`) was implemented and tested on a `scadaproj` branch but is NOT - published to the package feed, and ScadaBridge does not consume it.** Publishing is an outward - side effect that needs explicit user consent, and it would be a dead pin here regardless — - hub retirement (above) removes ScadaBridge's only dependency on the hub client entirely. It - remains available for the library's other hub consumers once published. + `ISecretsHubSyncStatus`) is published to the Gitea feed (2026-09-28, after merge), but + ScadaBridge does not consume it** — hub retirement (above) removes ScadaBridge's only dependency + on the hub client, so it stays on 0.6.2. It is there for the library's other hub consumers + (OtOpcUa). - **Empty, not null, when a site references no secrets (Task 13 live-gate fix).** The command builder first shipped `Secrets = null` for a site with no references ("null-when-empty", borrowed from the hash convention). But the site treats `null` as "central shipped no secrets" and touches