Incident desk

A release job exploded. Start here.

The First Five Minutes#

Write down the consumer repository, the commit or tag, the Actions run URL, the StroggForge ref the caller pins, the failing job, the platform and the exact error. Then check which ref the consumer actually pins. A caller on @v43 gets v43's behavior, no matter what these pages say about the current tag.

Open the failing workflow's contract and find the job. Its needs and if tell you whether it failed or was skipped because something upstream failed first. Fix the first failure, not the loudest one.

Where to Look#

SymptomLook atDo
Release never publishedlint, testBuilds do not wait for the checks; publish does. Fix the first failing check.
Clippy fails only with the release's features.stroggforge/cargo-build-args.sh, the test job's second ClippyCode is dead or broken in the feature set that platform ships. Gate it on the features that use it.
clang, lld and rustc disagreescripts/shared/setup-llvm.sh, rustc -vVMatch rustc's LLVM major. The MSRV job has to pass its own toolchain, or it gets stable's LLVM.
l3i refuses the build flagsthe consumer's .cargo/config.toml, L3i's TOOLCHAIN.mdclang, lld and -Clinker-plugin-lto go together. Cargo does not inherit a dependency's config, so every consumer carries its own.
Windows proc macro rejects -Clinker-plugin-ltoCARGO_BUILD_TARGET in the job logsetup-llvm pins the host triple. If something unset it, target rustflags reach proc macros again.
Windows binary "missing" after a green buildtarget/<triple>/releaseThat is where it went. Corprus Crucible knows; a hand-written step may not.
PortMaster binary links but will not runreadelf -V on the binary, the device's glibcThe floor is glibc 2.34 now. Devices that were happy with EL8 builds may not be.
Android LTO or codegen failureNDK r27c clang vs the host rustc's LLVMHost setup succeeding proves nothing about NDK bitcode compatibility.
Wrong manifest or binary builtresolve-build-context.sh, binary_names, binary_packageName the package explicitly instead of trusting directory detection.
Library crate not foundresolve-crate-manifest.sh, crate_namesUse the Cargo [package].name. Hyphens and underscores are normalized; typos are not.
Archive missing filescreate-release-archive.sh, include_filesReproduce the staging locally before uploading anything.
Signing failssign-release-binary.sh, id-token: writeWithout OIDC permission, keyless signing has no identity to sign with.
VirusTotal step failsVT_API_KEYNon-PR binary releases need it, even though the contract marks the secret optional.
Release assets vanishedthe publish job's refresh stepThe refresh deletes and recreates the release. Anything uploaded before it is gone.
crates.io 429 or missing dependencypublish_workspace.py, the job logIt retries and waits for the index already. Read the log before publishing by hand.
Cargo refuses a dirty treethe .stroggforge helper checkoutThe workflow copies the publisher to $RUNNER_TEMP and removes the checkout first. A custom step has to do the same.
Changelog empty or wrongfetch-depthIt needs full history.
Benchmark page emptygenerate-benchmark-docs.sh, Criterion JSONCheck that benchmarks ran before blaming the upload.
Pages overwrittenpublish_docsrustdoc and a project's own site cannot both own Pages. Pick one.
Nexus upload failsNEXUS_API_KEY, NEXUS_GROUP_IDSCheck the group ID for that exact OS and architecture.
AUR update failsthe AUR environment, package name, SSH keyUsually ownership or key access.
Discord says success after a failurenotify.needsEvery job that can fail a release belongs in that list. A missing webhook skips on purpose.
War room build rejects the TOMLthe error messageIt names the record and the reference. Fix war-room/*.toml, never the generated pages.

The Ref Contract#

A workflow that calls .stroggforge/scripts/... needs a StroggForge checkout containing that script, and a composite action needs its scripts in the tagged tree. The YAML validates fine either way. Before blaming the command that failed, check that the tagged files are there at all.

Asking for Help#

Open the issue in the consumer repository if the problem is specific to it, or in StroggForge if the shared pipeline is at fault. Include the first-five-minutes notes, a minimal reproduction, and which channels already published. crates.io does not un-publish because you deleted a GitHub Release. Lua and content failures go to St4sh, not the Rust supply line.