phoebus_os/.forgejo/workflows/ci.yml
Phoebus 1d37fbc1b8 ci(release): fail closed and bind gates to the candidate artifact
Make a passing CI/release result mean the checks actually ran.

- .forgejo/workflows/ci.yml is fail-closed: it provisions the pinned
  toolchain or fails, then runs one 'make ci' (fmt-check, clippy, workspace
  tests, VM-harness safety tests, release build, static installer build).
- Pin stable Rust 1.93.1 in installer-rs/rust-toolchain.toml; run cargo gates
  with --locked for reproducible dependencies.
- phoebus-release gates now records passed/failed/blocked/skipped/not_run
  (only passed is a pass), executes real host gate commands, and imports the
  existing VM-harness results.json instead of a competing harness. Gates with
  no automation are always blocked.
- Bind gate reports and harness evidence to a candidate name+SHA-256
  (--candidate; PHOEBUS_VM_ARTIFACT[_SHA256]); stale or unbound evidence is
  failed, never passed.
- publish refuses unless the report is candidate-bound and all-passed, the
  manifest verifies the artifact and a detached signature verifies; atomic
  publish preserves and restores the previous release on failure.
- vmsafety.Results records the verified artifact digest; 3 new Python tests.
- 20 new Rust regression tests; ADR 0012 and docs updated.

Verified locally: make ci (364 Rust tests, 19 harness tests, release and
static builds) exit 0; static binary is static-pie linked. CI runner, VM and
model gates remain unexecuted here.
2026-09-22 07:34:27 -07:00

51 lines
1.7 KiB
YAML

# Forgejo Actions CI.
#
# This workflow mirrors the local quality gates exactly and is deliberately
# fail-closed: a required check that cannot run because a tool is missing fails
# the job rather than printing "skipping". A green job therefore means every
# listed check actually executed.
#
# The Rust toolchain is pinned in `installer-rs/rust-toolchain.toml`. The runner
# must provide either `rustup` (which installs the pin) or a cargo/rustfmt/clippy
# toolchain; the preflight below fails clearly otherwise.
#
# If your runner uses different labels, change `runs-on` accordingly.
name: ci
on:
push:
branches: [main]
pull_request:
concurrency:
group: ci-${{ github.ref }}
cancel-in-progress: true
jobs:
quality-gates:
runs-on: ubuntu-latest
timeout-minutes: 60
steps:
- uses: actions/checkout@v4
- name: Provision the pinned Rust toolchain
run: |
set -euo pipefail
if command -v rustup >/dev/null 2>&1; then
rustup show active-toolchain
rustup component add rustfmt clippy
rustup target add x86_64-unknown-linux-gnu
elif command -v cargo >/dev/null 2>&1; then
cargo --version
cargo fmt --version
cargo clippy --version
else
echo "ERROR: no Rust toolchain on this runner." >&2
echo "Install rustup (recommended, honours the pinned toolchain) or" >&2
echo "provide cargo with the rustfmt and clippy components, then retry." >&2
exit 1
fi
# One command for the whole gate set, identical to local development.
- name: Quality gates (fmt, clippy, tests, harness tests, builds)
run: make ci