Skip to content

[backport] Migrate Windows release signing to DigiCert STM keypair-alias - #14746

Open
cderv wants to merge 1 commit into
v1.10from
backport/14729-signing-stm
Open

[backport] Migrate Windows release signing to DigiCert STM keypair-alias#14746
cderv wants to merge 1 commit into
v1.10from
backport/14729-signing-stm

Conversation

@cderv

@cderv cderv commented Jul 31, 2026

Copy link
Copy Markdown
Member

Important

Backport of #14729 to the v1.10 release line.

The Windows signing cert active through mid-2026 is rotating to a keypair-alias model. The old signtool /sha1 $CERT_FINGERPRINT + smctl windows certsync path and its pre-2026 secrets stop working, so a v1.10 patch built with the current workflow would fail Windows signing. This cherry-picks #14729, switching make-installer-win to smctl sign --keypair-alias with the _2026 credential set. The os dispatch input and the partial-platform publish guard ride along in the same commit. See #14729 for the full detail.

@posit-snyk-bot

posit-snyk-bot commented Jul 31, 2026

Copy link
Copy Markdown
Collaborator

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@cderv

cderv commented Jul 31, 2026

Copy link
Copy Markdown
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants