Use published sign.exe CLI and 3rd part certificate extractor tools by mjcheetham · Pull Request #1647 · git-ecosystem/git-credential-manager (original) (raw)
added 3 commits
Use a 3rd party tool to extract the NuGet signing certificate for upload rather than relying on an option added to the sign.exe tool in a private fork.
Use the dotnet tool install command to acquire the code signing tool,
rather than rely on our Azure blob store.
Drop the -d and -u options from the sign.exe CLI; they are no longer
required.
mjcheetham added a commit that referenced this pull request
Changes:
- Update MSAL and Avalonia to latest versions (#1640).
- Changes to release workflow to publish NuGet signing certificate (#1594, #1644, #1647).
- Updates to Managed Identity and Service Principal docs.
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
[ Show hidden characters]({{ revealButtonHref }})