Skip to content

Releases

v0.11.10

Choose a tag to compare

@zsobpeter-code zsobpeter-code released this 11 Nov 16:12

0.11.10 — 2026-11-06

  • An MCP client configuration named .grok/config.toml is never a contract, as in @coderifts/contract-path (contract-write.cjs:69, app commit 2c7f503e, P65). src/contract-path.js:25 MCP_CLIENT_CONFIG gains the |\.grok\/config\.toml alternative; before, the pattern lacked it and test/contract-path-mirror.test.js:48 (MIRROR) was red against the package.
  • Vendored core: receipt-verifier v1.0.3 → v1.2.1 (signed tag, peeled e1a346b). src/verify.js and src/verify-grant.js are byte copies of the tag; the other ten pinned .js files were already byte-identical to it, receipt-from-commit.js included (src/VENDOR.sha256). The verdict changes this brings, by the receipt-verifier release that made them: 1.1.1 a v1–v3 receipt is not authorization (P66) and a non-string signed field is MALFORMED; 1.1.4 a receipt verified beside an envelope must be v4; 1.1.5 Ed25519 only, and the result names the key that verified; 1.1.6 --as-of audit evaluation, and expiry applies under a retired key; 1.1.7 strict JSON parse (duplicate keys, lone surrogates, non-finite numbers are MALFORMED), and in verify-grant.js a grant whose key has revoked_at refuses at every instant and grant bodies are parsed strictly; 1.1.8 an --as-of instant before the receipt's ts is NOT_YET_VALID_AT_AS_OF; 1.2.0 the RECEIPT_FORMAT §7.1 key-status order — a revoked key is REVOKED_KEY at every signing time (with compromised_at in the result) and wins over retired_at, REVOKED_KEY_UNDECIDABLE is withdrawn, and a retired key signed before retired_at with no time anchor is RETIRED_KEY_UNANCHORED: valid:true → valid:false (was RETIRED_KEY_VALID_AT_ISSUE). The xlang corpus is regenerated with the receipt-verifier generator.

v0.11.9

Choose a tag to compare

@zsobpeter-code zsobpeter-code released this 12 Oct 11:40

0.11.9 — 2026-10-12

  • Sends control-plane artifacts; v4-only receipts; a control-plane-only diff can now go green with two bound approvals and red without them. For every changed control-plane path the authorize request carries { id, type: "control_plane", before, after } beside any contract artifacts. Paths come from git diff -z --no-renames --name-only <base> <head>, so a rename is a delete of the old path plus an add of the new one. Keys and signing material under .coderifts/keys/, .coderifts/trust/, .coderifts/signing/, and .pem/.pub under .coderifts/ are sent as the path only (before and after are ""); the file text is not read. The list is src/control-plane.js, the same list as coderifts-app src/mergegate/control-plane.js lines 58-100 (read 2026-10-12): top-level .github/workflows/*.yml|yaml, .coderifts.yml/.yaml, those key paths, .coderifts/audit.yml|yaml, coderifts-audit.yml|yaml, keyring/pinned-keys.json, a root action.yml|yaml, and .github/actions/**. A request missing preflight_mode: authorize, repository, base, head, or operation: merge is not sent (invalid_context, and the summary names the slot). The issued receipt is still judged by judgeReceipt (four-slot binding, v4-only). REQUIRE_APPROVAL or BLOCK is receipt_not_allow, and the title carries CONTROL_PLANE_CHANGE.

v0.11.6

Choose a tag to compare

@zsobpeter-code zsobpeter-code released this 11 Oct 11:59
  • 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.

v0.11.5

Choose a tag to compare

@zsobpeter-code zsobpeter-code released this 09 Oct 14:25

P65d: a plain mcp.json that is both an MCP client configuration (mcpServers or servers) and a tool manifest (tools), or that does not parse as JSON, is not read from git and not sent; the run fails with outcome MCP_JSON_HELD and one sentence naming the file. A plain mcp.json with mcpServers or servers and no tools stays a client configuration (counted as no file); a file with tools only stays a contract. The mirror follows @coderifts/contract-path 1.3.1.

v0.11.4 — a plain mcp.json is decided by its content

Choose a tag to compare

@zsobpeter-code zsobpeter-code released this 08 Oct 08:15

P65c: by name the Action refuses only .mcp.json, .cursor/mcp.json, .vscode/mcp.json, claude_desktop_config.json and (cline_)mcp_settings.json (never read). Any other mcp.json is read with git show and decided as @coderifts/contract-path 1.3.0 decides it: mcpServers/servers and no tools → an MCP client configuration, counted as no file and never sent; tools, any other shape, or unparseable → a contract (fail-closed). A server's tool manifest named mcp.json is a contract again. Pin: 9359e7f

v0.11.3 — an MCP client configuration is never read or sent

Choose a tag to compare

@zsobpeter-code zsobpeter-code released this 06 Oct 19:50

P65: mcp.json, .cursor/mcp.json, .vscode/mcp.json, mcp_settings.json, cline_mcp_settings.json, .mcp.json and claude_desktop_config.json are not contract artifacts; the Action does not read them from git or send them to preflight. Pin: 97d4cea

v0.11.2 — the reader, described

Choose a tag to compare

@zsobpeter-code zsobpeter-code released this 01 Oct 13:42

No behaviour change. The action.yml description now says what the reader profile does: with a trailer, verifies the receipt offline against the pinned keyring; without one, issues a receipt with the repository key, verifies it the same way and puts it in the check summary — never in the commit. Two required contexts: CodeRifts / contract-gate (this Action) and CodeRifts / issuer (the App).

v0.11.0 — the reader is the required check

Choose a tag to compare

@zsobpeter-code zsobpeter-code released this 28 Sep 05:44

With a valid CodeRifts-Receipt trailer + sidecar the Action verifies the receipt offline against the pinned keyring and never calls the issuer. Without a trailer and with a key it issues a receipt, verifies it the same way and puts it in the check summary — never in the commit. Two required contexts: CodeRifts / contract-gate (this Action) and CodeRifts / issuer (the App). The customer workflow listens to merge_group. Five negative cases fail closed; skipped or timed-out runs do not pass.

v0.10.0 — require-receipt-trailer

Choose a tag to compare

@zsobpeter-code zsobpeter-code released this 26 Sep 17:46

require-receipt-trailer: off by default; when on, the head commit's receipt must verify offline, match the diff digest and be a continue

v0.9.4 — check output cites the grant_id and receipt-digest

Choose a tag to compare

@zsobpeter-code zsobpeter-code released this 10 Sep 15:28

The check output cites the grant_id and receipt-digest with a travelling scope claim. The grant_id (from the verified payload) and the receipt-digest appear in the human summary and a coderifts-citation block; does_not_prove travels with the token (the digest does not mean the merge happened, CI passed, or any third party witnessed it).