When to use this skill
ALWAYS use this skill when the user mentions:
- Production builds or packaging
- Signing or release artifacts
- CI pipelines for distribution
Trigger phrases include:
- "build", "release", "signing", "distribution", "pipeline"
- "构建", "发布", "签名", "分发", "流水线"
How to use this skill
- Identify target platforms and packaging formats
- Configure release build and signing requirements
- Produce installers or app bundles per platform
- Validate release artifacts and update channels
Outputs
- Release build checklist
- Signing and distribution plan
Scope
- Boundary: Build, signing, and distribution only
- Key points: Debug vs release and platform packaging
References
- https://v2.tauri.app/llms.txt
- https://v2.tauri.app/distribute/
- https://v2.tauri.app/distribute/app-store/
- https://v2.tauri.app/distribute/appimage/
- https://v2.tauri.app/distribute/aur/
- https://v2.tauri.app/distribute/crabnebula-cloud/
- https://v2.tauri.app/distribute/debian/
- https://v2.tauri.app/distribute/dmg/
- https://v2.tauri.app/distribute/flatpak/
- https://v2.tauri.app/distribute/google-play/
- https://v2.tauri.app/distribute/macos-application-bundle/
- https://v2.tauri.app/distribute/microsoft-store/
- https://v2.tauri.app/distribute/rpm/
- https://v2.tauri.app/distribute/snapcraft/
- https://v2.tauri.app/distribute/windows-installer/
- https://v2.tauri.app/distribute/sign/macos/
- https://v2.tauri.app/distribute/sign/windows/
- https://v2.tauri.app/distribute/sign/linux/
- https://v2.tauri.app/distribute/sign/ios/
- https://v2.tauri.app/distribute/sign/android/
- https://v2.tauri.app/distribute/pipelines/crabnebula-cloud/
- https://v2.tauri.app/distribute/pipelines/github/
Keywords
tauri build, release, signing, packaging, distribution
Common Gotchas
- Version compatibility: Pay attention to compatibility between framework versions and dependency libraries; APIs may differ across versions
- Configuration file format: Configuration file format errors are the most common problem; it is recommended to use your editor's syntax checking
- Environment variables: Ensure all necessary environment variables are set correctly, and do not hardcode sensitive information
- Dependency conflicts: When multiple versions coexist, watch out for dependency conflicts and use a lock file to pin versions
- Performance pitfalls: In large-data scenarios, pay attention to performance optimization and avoid common issues such as N+1 queries
Usage workflow
Step 1: Environment preparation
Ensure the development environment has the necessary dependencies and tools installed.
Step 2: Configuration initialization
Perform basic configuration according to project requirements.
Step 3: Using core features
Implement the core functionality according to the example code.
Step 4: Test verification
Run tests to ensure the functionality works properly.
Step 5: Deployment and release
After development is complete, proceed with deployment and monitoring.