(@actions/attest) build provenance statement from OIDC claims #1693
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.
Updates the
attestProvenance
function in the@actions/attest
package so that the provenance statement is populated from data read from a verified GHA OIDC token.Previously, the provenance data was read directly from the environment. With the new approach, an OIDC token is retrieved from the GHA issuer and the provenance statement is built from the claims present in that token. This more closely mirrors the approach that is used by Sigstore certificate authority (Fulcio) when it populates the claims in the signing certificate.