Sign Windows release artifacts with Azure Artifact Signing - #284
Merged
Conversation
mando
force-pushed
the
windows-artifact-signing
branch
from
July 16, 2026 20:57
659ce36 to
3e14bd5
Compare
mando
force-pushed
the
windows-artifact-signing
branch
from
July 17, 2026 15:11
a950717 to
9d65ed6
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Required GitHub configuration
Secrets:
AZURE_CLIENT_IDAZURE_TENANT_IDAZURE_SUBSCRIPTION_IDAZURE_ARTIFACT_SIGNING_ENDPOINTAZURE_ARTIFACT_SIGNING_ACCOUNTAZURE_ARTIFACT_SIGNING_PROFILEThe Azure identity must have the Artifact Signing Certificate Profile Signer role and a GitHub OIDC federated credential.
Verification
vars.*while the configured values are repository secrets; that is corrected in the latest commit