Verification and release builds start together: one lint job (fmt, audit, MSRV, packaging dry runs), a test job per desktop that runs Clippy twice (every feature, and the features its release ships) and the tests, and the platform builds, of which Android and PortMaster lint their own cross builds. The tests run the default cargo test targets (library, binaries, integration tests, doctests, examples built), never the benches, which Clippy lints. publish runs only when all of them pass: it packs muOS apps, refreshes the GitHub Release, uploads archives and the changelog, and on tags opens dependent issues. Tags publish crates. Nexus uploads, AUR, rustdoc and the Mod Template stage follow publish; a pull request checks its site from the start instead (site-check). Benchmarks run on tags with generate_benchmarks, through benchmarks.yml.
Compiler/LLVM major mismatch: inspect rust-setup, setup-llvm.sh and the platform matrix.
Clippy with the features the release ships fails where Clippy with every feature passes: code dead or broken in that platform's feature set, from .stroggforge/cargo-build-args.sh.
Missing VT token, signing OIDC permission, Nexus group IDs or registry token: inspect the failing stage, not the archive name.
A failed test or lint on one platform holds back publish even though every build finished: builds do not wait for tests, publishing does.
Cargo package that provides the binaries, built from the repository root with --package <name> --bin <binary>. Set workspace to build with --workspace --bin <binary>. Empty keeps directory detection.
cargo_publish
boolean
false
true
Publish to crates.io on tagged releases; run a dry-run on all other pushes. Requires CARGO_REGISTRY_TOKEN secret.
cargo_publish_workspace
boolean
false
false
Publish every publishable workspace member in dependency order instead of one crate per binary name. Skips versions already on crates.io and waits out crates.io rate limits.
dependent_repo_names
string
false
Dependent repositories to notify on tagged releases, one owner/repo per line. JSON arrays are still accepted for compatibility.
development_release
string
false
development
The rolling pre-release, and its tag, that pushes to the default branch refresh. Change it only when that name can't be used, such as a tag GitHub keeps for an immutable release.
enable_android
boolean
false
false
Build and publish Android ARM64 ELF release artifacts targeting Android API level 23. This does not build an APK.
enable_portmaster
boolean
false
false
Build and publish Portmaster ARM64 release artifacts targeting aarch64-unknown-linux-gnu cross-compiled with clang and lld against an EL9 (glibc 2.34) sysroot.
generate_benchmarks
boolean
false
false
Run cargo bench, generate BENCHMARKS.md from Criterion output or the raw benchmark log, and upload it to the release.
generate_changelog
boolean
false
true
Generate a CHANGELOG.md from git history and upload it to the release.
generate_discord_notification
boolean
false
true
Generate a discord notification to DreamWeave upon success.
git_email
string
false
corleycomputerrepair@protonmail.ch
—
git_username
string
false
magicaldave
—
gpu_tests
boolean
false
false
Give the Linux tests a GPU: Mesa's software Vulkan driver (lavapipe), so tests that skip without an adapter run. macOS and Windows runners have one already.
include_files
string
false
README.md,LICENSE
Additional files or directories to include in platform archives (comma-separated).
mod_template
boolean
false
false
The repository is a DreamWeave Mod Template site. After the release is published, modGlobalBuild records its archives in mod.lock and builds and deploys the site. Replaces rustdoc Pages; the caller also grants actions: write.
msrv
string
false
Minimum supported Rust version to check the workspace against before release, e.g. '1.88'. 'auto' reads rust-version from Cargo.toml. Empty skips the check.
muxapp_dir
string
false
A directory in the repository holding muOS app files (mux_launch.sh and the rest). Each PortMaster archive is packaged with them as <binary>-Portmaster-ARM64.muxapp and published beside it. Requires enable_portmaster.
publish_docs
boolean
false
true
Build cargo doc and deploy to GitHub Pages. Disable if the project uses its own SSG.
body_file=.corprus-crucible/github-release-downloads/release-body.md : > "$body_file" shopt -s nullglob for vt_file in .corprus-crucible/github-release-downloads/*.vt.md; do if [ -s "$vt_file" ]; then printf '%s\n' "$(< "$vt_file")" >> "$body_file" fi done echo "body_path=$body_file" >> "$GITHUB_OUTPUT"