feat(ci): attest nuget release artifacts#203
Merged
Merged
Conversation
Add GitHub artifact attestation permissions and an actions/attest step in the deploy job so release nupkg artifacts include signed provenance metadata.
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.
Why
We already use OIDC trusted publishing to nuget.org, but release artifacts did not have GitHub-signed provenance metadata. Adding attestation strengthens supply-chain integrity and gives maintainers and consumers a way to verify where the published package came from.
What changed
attestations: writeandartifact-metadata: writepermissions to thedeployjob indeploy.yml.actions/attest@v4step that attests the builtIntelliTect.Multitool.<tag>.nupkgbefore NuGet push and release upload.Notes