Release pipelines

From Git state to artifacts, with conditional lanes intact.

Binary release#

The caller decides which events invoke the workflow. This is the exact needs graph; the contract lists every if guard.

workflow-rustGlobalBuild relationship diagram. Its textual ledger or workflow contract is on this page or linked below.
workflow rustGlobalBuild · Mermaid source · Full-size SVG
Read diagram source
flowchart TD
  n_aur["aur"]
  n_benchmarks["benchmarks"]
  n_crates["crates"]
  n_docs["docs"]
  n_lint["lint"]
  n_mod_template["mod-template"]
  n_nexus["nexus"]
  n_notify["notify"]
  n_publish["publish"]
  n_release["release"]
  n_release_android["release-android"]
  n_release_linux["release-linux"]
  n_release_portmaster["release-portmaster"]
  n_site_check["site-check"]
  n_test["test"]
  n_publish --> n_aur
  n_publish --> n_benchmarks
  n_lint --> n_crates
  n_test --> n_crates
  n_release --> n_crates
  n_release_linux --> n_crates
  n_release_android --> n_crates
  n_release_portmaster --> n_crates
  n_lint --> n_docs
  n_test --> n_docs
  n_publish --> n_mod_template
  n_crates --> n_mod_template
  n_publish --> n_nexus
  n_lint --> n_notify
  n_test --> n_notify
  n_release --> n_notify
  n_release_linux --> n_notify
  n_release_android --> n_notify
  n_release_portmaster --> n_notify
  n_publish --> n_notify
  n_nexus --> n_notify
  n_crates --> n_notify
  n_aur --> n_notify
  n_docs --> n_notify
  n_benchmarks --> n_notify
  n_mod_template --> n_notify
  n_lint --> n_publish
  n_test --> n_publish
  n_release --> n_publish
  n_release_linux --> n_publish
  n_release_android --> n_publish
  n_release_portmaster --> n_publish

Library release#

Quality gates precede release_cleanup; publishing and release material follow their job prerequisites. No binary signing or packaging.

workflow-libGlobalBuild relationship diagram. Its textual ledger or workflow contract is on this page or linked below.
workflow libGlobalBuild · Mermaid source · Full-size SVG
Read diagram source
flowchart TD
  n_benchmarks["benchmarks"]
  n_crates["crates"]
  n_docs["docs"]
  n_lint["lint"]
  n_mod_template["mod-template"]
  n_notify["notify"]
  n_publish["publish"]
  n_site_check["site-check"]
  n_test["test"]
  n_publish --> n_benchmarks
  n_lint --> n_crates
  n_test --> n_crates
  n_lint --> n_docs
  n_test --> n_docs
  n_publish --> n_mod_template
  n_crates --> n_mod_template
  n_lint --> n_notify
  n_test --> n_notify
  n_publish --> n_notify
  n_crates --> n_notify
  n_docs --> n_notify
  n_benchmarks --> n_notify
  n_mod_template --> n_notify
  n_lint --> n_publish
  n_test --> n_publish

Trigger boundaries#

  • Pull request: quality and build checks; no signing, scanning or release upload.
  • Main push: quality checks and configured rustdoc Pages. Non-tag releases use the rolling development release.
  • Tag: configured crates.io publication and a named GitHub Release.
  • AUR: configured push path after platform success; not restricted to tags.
  • Nexus: configured non-PR path after platform success; needs the secret pair and group IDs.
  • Android/PortMaster: opt-in native artifacts, not APKs or a PortMaster catalog submission.

Publishing and recovery · Supply-chain stages