Add Linux and Windows code signing to release workflow #6637
Conversation
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
shijie-oai
force-pushed
the
codex/add-code-signing-support-for-linux-and-windows
branch
2 times, most recently
from
a83b76a to
065fbe9
Compare
shijie-oai
force-pushed
the
codex/add-code-signing-support-for-linux-and-windows
branch
from
dac1fb7 to
8fe206d
Compare
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.
Summary
install Sigstore cosign during Linux release builds and produce
.sigstorebundles for each binaryrun Azure Trusted Signing for Windows targets and publish the resulting signatures alongside the artifacts
document the new signing requirements in the release management guide
Swap out
AZURE_TRUSTED_SIGNING_CLIENT_IDfor release flow.