CI / fmt + clippy + test (Linux x86_64) (push) Waiting to run
CI / schema instance validation + consumers (push) Waiting to run
CI / runtime contract (macos-latest) (push) Waiting to run
CI / runtime contract (windows-latest) (push) Waiting to run
Linux strict security lane (G-C) / strict isolation escape matrix (push) Waiting to run
ci/woodpecker/push/woodpecker Pipeline was successful
Add tools/ci/release_evidence.py (marqdo.release-gates.v1) plus unit tests: missing/skipped/FAIL/UNVERIFIED and tested_sha mismatches stay DO_NOT_RELEASE, performance may be PASS/WARN, unknown gate names are rejected. The GitHub CI now has a release-evidence job that maps the Linux/schema and native matrix results onto the manifest and uploads it, and both CI systems run the evidence-tool tests. Clear the contradictions the RFC calls out: remove the stale CURRENT.md rows that claimed DNS/TLS/UDP and fs metadata were absent while the same table said they were implemented; correct docs/ci.md to state that the GitHub-hosted Windows/macOS matrix exists (Woodpecker has no such agent); keep the old convergence plan historical; require the evidence manifest in releasing.md; and add a docs-consistency guard for these claims. This is step 6 of the CI/security RFC (B05/B06/B07).
22 lines
1003 B
Markdown
22 lines
1003 B
Markdown
# CI release-evidence manifests
|
|
|
|
`docs/evidence/ci/<full-40-hex-sha>/manifest.json` is generated by
|
|
`tools/ci/release_evidence.py` (schema `marqdo.release-gates.v1`) and uploaded
|
|
by the `release-evidence` CI job. Do not hand-edit a manifest into `PASS`.
|
|
|
|
Rules:
|
|
|
|
* every gate records its own `tested_sha`; it must equal `target_sha`;
|
|
* skipped, cancelled, queued, timed-out, missing or older-SHA jobs are
|
|
`UNVERIFIED`/`FAIL`, never `PASS`;
|
|
* `strict_vm` needs a real disposable-VM `strict-evidence.json` (schema
|
|
`marqdo.strict-evidence.v1`) with `outcome: PASS`, non-root `uid` and the
|
|
same SHA; a URL alone is not enough;
|
|
* `performance` needs a `MEASURED` report from the fixed node; TCG/QEMU or
|
|
development-container numbers are not a baseline;
|
|
* `release_decision` is `RELEASE_CANDIDATE` only when every required gate is
|
|
PASS with the same SHA and performance is PASS/WARN. Anything else is
|
|
`DO_NOT_RELEASE`.
|
|
|
|
The manifest is evidence, not permission to tag; owner approval is separate.
|