Skip to content

Reference: Multi-Platform Build Flows

This page is the Diataxis reference entry for the current multi-platform build matrix that underpins the Git LFS migration.

Canonical Source

What This Reference Covers

  • source web build and explicit full-graph build behavior
  • desktop Tauri dev/bundle flow and sidecar ownership
  • Android Capacitor packaging flow
  • Android Tauri native runtime/build flow
  • GitHub Release, npm publish, and docs-site delivery pipelines

Current High-Signal Conclusions

  • The default source build contract is runtime-first.
  • Explicit full-mode remains supported, and Tauri full bundles now preserve that mode through beforeBuildCommand.
  • Desktop bundles still treat sidecar binaries as a separate bootstrap concern.
  • Mobile packaging and mobile runtime capability must be evaluated separately.
  • Docs and npm publish pipelines are already compatible with the current no-new-LFS direction.
  • Release smoke on 2026-04-08 already proved the workflow can cold-create and seed the project-controlled godot-mirror-v4.3-stable tag before desktop bundle jobs run.
  • The current release workflow now pins the mirrored Windows, Linux, and macOS Godot archives with fixed SHA256 values before use.
  • The same release workflow now exposes allow_godot_upstream_fallback so mirror-only smoke runs can disable upstream fallback without changing the default release path.
  • A non-blocking release-governance risk remains: GitHub Actions currently warns that actions/upload-artifact@v4 and softprops/action-gh-release@v2 are still Node 20-targeted.

Use This Reference When

  • deciding whether a migration item is safe across desktop, mobile, publish, and release surfaces
  • checking whether a build command is runtime-first or explicit full-mode
  • verifying whether a platform still depends on repo-head LFS assets