Sign releases, dev builds, and nuget package #4189
Merged
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.
Motivation
SignPath's action is ready, we have a certificate, and #4188 created a helper build target to collect assets for signing. The next step toward signing releases is updating our workflows.
Changes
build.yml
uses the build target from Add Prepare-SignPath target to build script #4188 to upload an artifact containing the assets we need to sign for the Release configurationsign.yml
is created to retrieve that artifact, get it signed, and upload a newsigned
artifact with the resultsrelease.yml
callssign.yml
to generate signed assets for releasesdeploy.yml
callssign.yml
to generate signed assets for uploading dev builds