Repository navigation
ci: allow the release job to create attestations - #34
Merged
Merged
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
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.
What and why
Releases will carry a source archive with signed SLSA build provenance created by
actions/attestin the reusablerelease.ymlofsogeor/workflows. A reusable workflow cannot get more permissions than its caller, so thereleasejob now grantsattestations: writeandid-token: write(OIDC for Sigstore signing). The workflow-level permissions staycontents: read; the current reusable workflow does not use the new permissions yet.How it was tested
pre-commit run --all-files(yamllint, actionlint checks in CI).Checklist
feat:,fix:,feat!:for breaking changes)pre-commit run --all-filespasses locallySecret/*.sops.yamlis SOPS-encrypted