Use new DigiCert KeyLocker workflow for signing Ark on Windows - #1359
Merged
Conversation
lionel-
approved these changes
Jul 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ark for Windows is currently signed using a certificate that expires in less than a month (August 19). Unfortunately, this certificate can't be replaced as-is because DigiCert has changed their service.
I've added a new shared action to sign using the new workflow here:
https://github.com/posit-dev/posit-gh-actions/blob/main/.github/workflows/sign-windows-digicert.yml
This change updates Ark to use the new certificate and workflow from the shared action.