Update release workflow to use Windows Trusted Signing Action#5873
Merged
chrisd8088 merged 1 commit intogit-lfs:mainfrom Sep 30, 2024
Merged
Update release workflow to use Windows Trusted Signing Action#5873chrisd8088 merged 1 commit intogit-lfs:mainfrom
chrisd8088 merged 1 commit intogit-lfs:mainfrom
Conversation
The azure/azure-code-signing-action repository has been removed and replaced with the azure/trusted-signing-action repository, so we update our release GitHub Actions workflow to use the latest version of the new action.
larsxschneider
approved these changes
Sep 30, 2024
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
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.
The
azure/azure-code-signing-actionGitHub repository has been removed and replaced with theazure/trusted-signing-actionrepository, so we update our release GitHub Actions workflow to use the latest version of the new action.This PR's changes have been tested with a successful run of our release workflow in a private repository.