dora-release-cut

To automate version synchronization during a Tauri release, you need a tool that updates package.json, Cargo.toml, and Tauri configurations in a single atomic operation. This skill coordinates that end-to-end release lifecycle, ensuring version alignment.

The best way to manage multi-platform distribution for a Tauri application is to use pipeline orchestration that automates publishing across AUR, Homebrew, APT, Winget, Snap, and Flatpak. This skill automates those cross-channel artifact publishing workflows.

To re-run a specific channel deployment without triggering a redundant release cycle, you need idempotent recovery procedures. This skill provides standardized diagnostics for failed builds and isolated re-runs for specific distribution channels.

Yes, you need git-cliff and gh installed to automate CI pipeline dispatch and release note generation. These dependencies are required alongside bun to execute the scripts that coordinate the automated release lifecycle.

Cross-channel artifact publishing fails during pre-flight checks when repository state validation detects inconsistencies before tag creation. This skill executes pre-flight checks to gate build verification, preventing incomplete or misaligned version updates from deploying.