Repository navigation
ci: add trusted Guard attestations with v0.14.0 - #26
Merged
Merged
Conversation
vladzdev
marked this pull request as ready for review
November 9, 2026 12:14
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 this adds
pull_request_targetverifier from the released 0.14.0 template.c060de9f834d05f74ee6666508c23fa698b625c0using the repository Actions variables, which are already configured.codapult-guard.ymlworkflow and assigns Guard policy files to the repository's existing CODEOWNERS.Guard 0.14.0 verification of the new policy contract passes locally (
ciIntegrity.status=ok).Before and after merge
mainis currently unprotected. The active branch rulesets API does not show a rule for it, and the existingTest merge queueruleset is disabled. The token used for this setup cannot create repository rulesets (GitHub requiresAdministration: write).Before merging, protect
mainwith a repository ruleset that requires one independent approval, CODEOWNER review for.github/**and.codapult/guard/**, and the existingArchitecture Guardcheck. After this workflow has merged and emitted its check, addGuard trusted verificationas a required check. Keep project tests/builds required separately when those workflows are enabled.After merge, open a same-repository PR to produce and download the signed
.intoto.jsonland.sigstore.jsonlartifacts. The setup PR itself cannot produce its own trusted attestation because GitHub loadspull_request_targetworkflows from the default branch.