Publishing and recovery

What a tag sets in motion, and how not to make a half-finished release worse.

Before You Tag#

Put the release in a plan first: version, platforms, channels, and what has to be true before it ships. Check which StroggForge ref the consumer pins and which inputs it passes. The version in Cargo.toml is not a plan, and the war room never creates tags for you. Release Planning has the manual checklist for Rust applications.

Where Things Get Published#

DestinationWhenNeeds
GitHub ReleaseAfter every platform build is staged; the release is refreshed firstcontents: write; for binaries, signing and scanning setup
crates.ioTags, when publishing is enabledCARGO_REGISTRY_TOKEN, a correct package version
crates.io, whole workspaceTags with cargo_publish_workspaceDependency order and index visibility, both handled by the publisher
Rustdoc on PagesMain pushes with publish_docs, after the gatesPages source set to Actions, Pages and OIDC permissions
Changelog and benchmarksAfter the release refreshFull Git history for the changelog; benchmarks are opt-in
AURConfigured pushes after the platform buildsPackage name, SSH key, the AUR environment
NexusConfigured non-PR runs after the buildsAPI key plus a file group ID per platform
PortMasterOpt-in ARM64 native binaryA device that runs it. Catalog submission is a separate, manual step.
muOS appOpt-in .muxapp of the PortMaster build, with muxapp_direnable_portmaster, and the app's files in the repository
Mod Template siteWith mod_template, after the GitHub Release or crates.io publishactions: write for the caller; the site's mod.lock on the default branch is committed by CI
AsHyAmSWithin six hours of the site deploying; nothing to triggerThe site enrolled in AsHyAmS's network/sources.toml, and a schema AsHyAmS already reads

A Partial Release Is Not a Clean Slate#

Refreshing a GitHub Release deletes and recreates it; for development it deletes the tag too. That is intentional, and it means anything uploaded before the refresh is gone.

Before rerunning a failed release, find out what already went out. crates.io does not forget a version because you deleted the GitHub Release. The workspace publisher skips versions that are already published, retries rate limits and waits for the index, so read its log before reaching for cargo publish yourself.

Closing the Plan#

Link the Actions run, the artifact and any device test on the requirements they finish. Leave a blocker in place until its reason is actually gone. The site reports what was recorded; it does not go and check.

Release board · Pipelines · Incident desk