• v0.1.2 a9b45e277c

    v0.1.2 Stable

    gitea_admin released this 2026-07-02 15:49:25 +00:00 | 1338 commits to main since this release

    Splits per-commit CI from the expensive release work, and adds a deterministic
    "when to cut a release" signal — so a grind can fan out fast feature branches
    while fuzz + ReleaseSafe still run often, just not per-PR.

    Added

    • templates/base/pipeline-release-cadence.yaml — a trusted CWT (holds the
      Forgejo token, runs no project code) that a per-project CronWorkflow submits
      on a schedule. If staging advanced past the last release tag, it drops the
      -dev suffix in the version file, promotes the CHANGELOG [Unreleased]
      section to a dated one, and lands it — driving pipeline-staging release mode
      (deep fuzz + ReleaseSafe + packaging + promote). Idempotent no-op when staging
      == last tag, the version is already clean, or the tag exists.
    • projects/zerotea/release-cron.yaml — the zerotea release-cadence signal
      (0 */6 * * *, concurrency Forbid). Fuzz + ReleaseSafe now run every 6h when
      there are changes, not on every PR.

    Changed

    • projects/zerotea/build.sh — per-commit CI is now a FAST correctness gate:
      zig fmt --check + zig build test + a Debug zig build (compiles exe +
      fuzz harness) + a deterministic kcov coverage gate (src-scoped, floor 85%,
      today ~99.6%; degrades to a warning until the builder ships kcov). The deep
      fuzz pass + amd64/arm64 ReleaseSafe cross-compile + nfpm packaging are gated
      to release mode (clean x.y.z). config.yaml records the coverage floor +
      the 6h cadence.
    Downloads