Nightly Builds
What runs
Section titled “What runs”nightly-artifacts.yml
runs on schedule: + workflow_dispatch: only — never on a tag push —
and exercises the same build/package/smoke-test steps as
release-binaries.yml / release-gui.yml / release-installers.yml every
day, using a ref shaped nightly-YYYYMMDD (e.g. nightly-20260904) that
does not match the v* pattern those tag-triggered workflows fan out on.
Its single release-writing step is gh release create ... --draft --prerelease (idempotent: a second run the same day updates the existing
draft’s assets instead of creating a duplicate). See the workflow’s own
safety header for the full invariant list.
This is deliberately not a public release. A draft release is visible
only to repo collaborators with write access; it never fires release: published, so bundle-release.yml cannot fan out from it, and — because a
draft release does not create the underlying git tag ref until published —
no tag-push event fires either. Nothing in the workflow calls gh release edit/publish, deletes a release, or pushes a tag.
Three-Tier CI/CD & Scheduled Nightly Architecture
Section titled “Three-Tier CI/CD & Scheduled Nightly Architecture”Vox separates repository verification into three tiers so inner-loop developer feedback stays under 15 seconds while scheduled nightly workflows run exhaustive cross-OS, feature-matrix, and mutation suites:
| Tier | Surface | Entrypoint | Target Budget | Scope |
|---|---|---|---|---|
| Tier 1: Local Inner-Loop Gate | Git pre-push hook | vox ci pre-push | < 15s (measured ~1.1s) | Path-scoped to git diff against merge-base (origin/main). Runs dirty-only rustfmt --check, read-only line-endings (autofix = false), conditional ssot-drift, workflow guards, dirty-only vox-doc-pipeline --lint-only, dirty-only doctest-md, and affected-crate vox-drift-check. |
| Tier 2: Pull Request Merge Gate | .github/workflows/ci.yml | vox ci pre-push --ci | < 10m | Full workspace static verification (retired-symbol-check, canonical-map-verify, vox kb eval --gate, legacy-Mermaid ratchet, workspace rustfmt), affected-crate tests (vox ci affected-crates), and Linux build check. Redundant pull_request: triggers were removed from compile-matrix.yml. |
| Tier 3: Scheduled Nightly Suites | .github/workflows/*nightly*.yml & local-ci | local-ci nightly | Scheduled (02:00–06:00 UTC) | Exhaustive multi-OS compilation (cross-platform-check.yml), feature-powerset checks (nightly.yml), strict rustdoc, Miri, Cargo Deny, Semver checks on crates/_public.toml, GUI cross-OS tests (gui-cross-build.yml), live/offline harness eval (harness-eval-nightly.yml), mutation testing (mutation-nightly.yml), link checking (link_checker.yml), and multi-target release artifact builds (nightly-artifacts.yml). |
Machine-readable end-to-end remediation and verification proof for all seven scheduled nightly workflows is recorded in contracts/reports/nightly-e2e-run-proof.v1.json.
History: the removed nightly-tag.yml
Section titled “History: the removed nightly-tag.yml”An earlier version of this pipeline (nightly-tag.yml, removed) computed a
tag shaped v<workspace-version>-nightly.<build-number> and pushed it with a
NIGHTLY_TAG_TOKEN PAT specifically so the push would cross GitHub’s
loop-prevention rule (a GITHUB_TOKEN-authored tag push does not trigger
other workflows’ on: push triggers, but a PAT-authored one does). Because
that tag matched v*, pushing it fanned out to release-binaries.yml,
release-installers.yml, and release-gui.yml exactly like a real version
tag — and those workflows’ publish steps create a genuinely public release
unless every one of them sets draft: true. release-installers.yml’s
publish step did not, so once NIGHTLY_TAG_TOKEN was configured this
pipeline would have auto-published a public release every night — the
outcome this repo has repeatedly been told never to automate. nightly-tag.yml
was deleted for this reason, and crates/vox-cli-ci/src/release_draft_guard.rs
was extended to also scan run: script bodies (not just uses: steps) for
an unguarded gh release create so an equivalent script-based path can’t
reopen the same hazard silently.
Using a nightly build locally
Section titled “Using a nightly build locally”There is no public nightly release to fetch by tag. To try a nightly exercise build, pull the artifact directly from the workflow run (requires repo read access):
gh run download --repo vox-foundation/vox \ $(gh run list --repo vox-foundation/vox --workflow nightly-artifacts.yml -L 1 --json databaseId -q '.[0].databaseId') \ --name nightly-x86_64-unknown-linux-gnuor browse the draft release’s assets directly (visible to collaborators
only) via gh release view nightly-YYYYMMDD --repo vox-foundation/vox.
voxup install --tag <tag> still works for any real, published release
tag (e.g. a release-candidate v0.6.0-rc.4) — /releases/latest excludes
prereleases by definition, so --tag is the way to fetch one. It has no
nightly tag to target today.
Non-goals
Section titled “Non-goals”- No automatic, unattended creation of a public GitHub release from any
schedule or cron trigger — see
crates/vox-cli-ci/src/release_draft_guard.rsanddocs/src/adr/for the standing policy this protects. - This does not change what
voxup install/voxup updatedo by default (still latest stable via/releases/latest);--tagis opt-in. - No automatic local-machine nightly polling/auto-update.