From 981a66f33b8b3a23a64c0cd435fa64ecfb09ad97 Mon Sep 17 00:00:00 2001 From: bchanot Date: Tue, 13 Oct 2026 01:19:15 +0200 Subject: [PATCH] ci: workflows kept as prepared material, marked never executed; script paths under scripts/ No runner, secret or registry exists on the forge; the three files map onto the stages of pnpm check:all so a future runner calls the same scripts. --- .gitea/workflows/ci.yml | 25 ++++++++++++++++--------- .gitea/workflows/release-images.yml | 3 +++ .gitea/workflows/rust-advisories.yml | 2 ++ 3 files changed, 21 insertions(+), 9 deletions(-) diff --git a/.gitea/workflows/ci.yml b/.gitea/workflows/ci.yml index ed4b6eaa..aea4453a 100644 --- a/.gitea/workflows/ci.yml +++ b/.gitea/workflows/ci.yml @@ -1,10 +1,17 @@ -# Gitea Actions (same syntax as GitHub Actions). Runs on the self-hosted forge -# runner; no external provider. The check job covers the SQL layer through the -# PGlite harness (no Docker); the supabase job replays it on the real stack. +# Gitea Actions (same syntax as GitHub Actions), written for a self-hosted forge +# runner; no external provider. # -# Rust (plan R0, docs/development/RUST.md): every cargo command runs inside the -# reference builder image built from docker/rust-builder.Dockerfile, so CI and a -# developer machine use the same toolchain and the production VPS never needs Rust. +# STATUS 2026-10-13: PREPARED, NEVER EXECUTED. No runner, secret or registry is +# configured on the forge; the CI/CD decision is a separate step. Until then the +# same checks run on the development machine with `pnpm check:all` +# (scripts/check-all.sh), which a future runner can call as is. +# +# The check job covers the SQL layer through the PGlite harness (no Docker); the +# supabase job replays it on the real stack. Rust (plan R0, docs/development/RUST.md): +# in this file every cargo command runs inside the reference builder image built from +# docker/rust-builder.Dockerfile (the native toolchain of the development machine runs +# the same scripts), so a runner and a developer machine use the same compiler and the +# production VPS never needs Rust. name: ci on: @@ -20,11 +27,11 @@ jobs: - name: Reference Rust builder image (runner needs a Docker daemon) run: docker build -f docker/rust-builder.Dockerfile -t faunosteo_rust_builder:1.99.0 docker - name: fmt, clippy, tests, ts-rs export, cargo-deny (licenses, bans, sources) - run: bash docker/rust-run.sh bash docker/rust-check.sh + run: bash docker/rust-run.sh bash scripts/rust-check.sh - name: Committed TypeScript types match the Rust contracts run: git diff --exit-code -- packages/core-wasm/types - name: Browser module builds (size printed; the budget is asserted by the vitest proofs) - run: bash docker/rust-run.sh bash docker/wasm-build.sh + run: bash docker/rust-run.sh bash scripts/wasm-build.sh check: runs-on: ubuntu-latest @@ -38,7 +45,7 @@ jobs: run: corepack enable && corepack prepare --activate - run: pnpm install --frozen-lockfile - name: Browser module for the core-wasm proofs (same builder image as the rust job) - run: docker build -f docker/rust-builder.Dockerfile -t faunosteo_rust_builder:1.99.0 docker && bash docker/rust-run.sh bash docker/wasm-build.sh + run: docker build -f docker/rust-builder.Dockerfile -t faunosteo_rust_builder:1.99.0 docker && bash docker/rust-run.sh bash scripts/wasm-build.sh - run: pnpm typecheck - run: pnpm test:run - run: pnpm lint diff --git a/.gitea/workflows/release-images.yml b/.gitea/workflows/release-images.yml index 65f897c5..2c022198 100644 --- a/.gitea/workflows/release-images.yml +++ b/.gitea/workflows/release-images.yml @@ -18,6 +18,9 @@ # that never runs them (Step 27 operations). Known mutable references, to pin at Step 27: # the buildkit engine image of the builder, the base images of the Dockerfiles. # +# STATUS 2026-10-13: prepared, never executed. No runner, no registry and none of the +# secrets below exist on the forge yet; configuring them is the CI/CD step, not R0. +# # Secrets expected on the forge: REGISTRY (host, e.g. the Gitea container registry of this # forge), REGISTRY_USER, REGISTRY_TOKEN (write:package scope). Images are pushed as # //faunosteo_app: and faunosteo_worker:; the digests are diff --git a/.gitea/workflows/rust-advisories.yml b/.gitea/workflows/rust-advisories.yml index 52f24c2f..72c85cb9 100644 --- a/.gitea/workflows/rust-advisories.yml +++ b/.gitea/workflows/rust-advisories.yml @@ -1,6 +1,8 @@ # RustSec advisories, out of the blocking path on purpose (RUST_ARCHITECTURE_REVIEW VIII.3): # an advisory published for an unrelated crate must not redden every branch. The run is # nightly and manual; the release gate (Step 27) reads its last result. +# STATUS 2026-10-13: prepared, never executed (no runner on the forge yet). Locally: +# `bash docker/rust-run.sh cargo deny check advisories` or, natively, `cargo deny check advisories`. name: rust-advisories on: