Skip to content

v0.11.6

Choose a tag to compare

@zsobpeter-code zsobpeter-code released this 11 Oct 11:59
· 10 commits to main since this release
  • The enforcing reader binds the receipt to this run. After the digest check, judgeReceipt compares preflight_mode, repository, base, and head with mismatchReason (src/gate.js). A mismatch is mode_mismatch, repo_mismatch, base_mismatch, or head_mismatch, and it is a failure, not the missing-trailer fall-through. A trailer or sidecar skips a slot only when that slot is unbound. An issued receipt always compares all four, so a missing slot fails closed. On merge_group, base_mismatch or head_mismatch with require-receipt-trailer left false falls through to issuance for the queue SHAs. repo_mismatch and mode_mismatch stay failures. With the flag true, a mismatch stays a failure.
  • require-receipt-trailer: true fails closed before preflight. No verifying trailer or sidecar posts failure with reason receipt_trailer_required, on every profile, and the preflight fetch is not called. The default stays false: on the enforcing profile a missing trailer still falls through to issuance, and a missing key still fails receipt_trailer_missing.
  • The action job shows the receipt. It appends the five receipt lines, the conclusion, the receipt id (envelope.receipt_id when set, otherwise envelope.decision_id), target_id, expires_at, and the reason to GITHUB_STEP_SUMMARY, and sets outputs receipt-id, conclusion, reason, and title. The example aggregator prints those outputs. A job check-run's output cannot be set by this step. post-check-run: false still writes the summary and the outputs; it only skips the check-run POST.
  • The suggested workflow's permissions are contents: read and pull-requests: read. checks: write stays commented, for the variant that posts its own check. The action reads the diff with local git (src/artifacts.js) and, only when it posts, POST /repos/{owner}/{repo}/check-runs (src/check-run.js). It does not call the pulls API. The SHAs come from GITHUB_EVENT_PATH.
  • README "Where it stops". A fork pull request receives no CODERIFTS_API_KEY, so nothing is issued and the run fails closed unless the head carries a verifying trailer. The Actions-posted required context uses the workflow GITHUB_TOKEN (src/gate.js), so anyone who can edit .github/workflows/ can turn it green. That is why CodeRifts / issuer is the second required check. Put CODEOWNERS on .github/workflows/** and, where the org has one, an org-level required workflow. pull_request_target is not used and not recommended.