From d9df8eb34b0f8395f957b22cc49ba5ea3dff5b8a Mon Sep 17 00:00:00 2001 From: Kevin Yue Date: Thu, 19 Nov 2026 00:06:32 +0800 Subject: [PATCH] docs(windows): distinguish Authenticode keys from update signing keys --- packaging/windows/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packaging/windows/README.md b/packaging/windows/README.md index 23f721a..aeffb86 100644 --- a/packaging/windows/README.md +++ b/packaging/windows/README.md @@ -70,7 +70,7 @@ Environment deployment policies allow the `release/next` branch and `v*` tags. Repository variables supply `AZURE_SIGNING_CLIENT_ID`, `AZURE_TENANT_ID`, `AZURE_SUBSCRIPTION_ID`, `AZURE_SIGNING_ENDPOINT`, `AZURE_SIGNING_ACCOUNT`, `AZURE_SIGNING_PROFILE`, and `WINDOWS_SIGNING_PUBLISHER`. No Azure client secret -or signing private key is stored in GitHub. `build-windows.ps1 -Sign` requires +or Authenticode private key is stored in GitHub. `build-windows.ps1 -Sign` requires Microsoft's ArtifactSigning PowerShell module 0.1.20 and an Azure CLI login. The build verifies the publisher, certificate trust and timestamp on each signed file. The installer smoke test repeats those checks on the installed runtime