makepad-deployment

# Makepad Packaging & Deployment This skill covers packaging Makepad applications for all supported platforms. ## When to Use - You need to package, distribute, or automate deployment of a Makepad application. - The task involves desktop installers, APK/IPA builds, WebAssembly output, or CI-based release artifacts. - You need guidance on `cargo-packager`, `cargo-makepad`, or GitHub Actions packaging flows for Makepad. ## Quick Navigation | Platform | Tool | Output | |----------|------|--------| | [Desktop](#desktop-packaging) | `cargo-packager` | .deb, .nsis, .dmg | | [Android](#android) | `cargo-makepad` | .apk | | [iOS](#ios) | `cargo-makepad` | .app, .ipa | | [Web](#wasm-packaging) | `cargo-makepad` | Wasm + HTML/JS | | [CI/CD](#github-actions-packaging) | `makepad-packaging-action` | GitHub Release assets | --- ## GitHub Actions Packaging Use `makepad-packaging-action` to package Makepad apps in CI. It wraps `cargo-packager` (desktop) and `cargo-makepad` (mobile), and can upload artifacts to GitHub Releases. ```yaml jobs: package: runs-on: ubuntu-22.04 steps: - uses: actions/checkout@v4 - uses: Project-Robius-China/makepad-packaging-action@v1 with: args: --target x86_64-unknown-linux-gnu --release ``` Notes: - Desktop packages must run on matching OS runners (Linux/Windows/macOS). - iOS builds require macOS runners. - Android builds can run on any OS runner. Full inputs/env/outputs and release workflows live in `reference...