Deploy - trigger Build & Release

Args: $ARGUMENTS (force / no-force override the auto-decision; empty = decide automatically).

Context

• Repo: patrickjaja/claude-desktop-extra · Workflow: build-and-release.yml · default branch: master.
• Current branch: !git branch --show-current
• Tracked upstream version: !cat .upstream-version 2>/dev/null
• Last release: !gh -R patrickjaja/claude-desktop-extra release list --limit 1 2>/dev/null || echo "(gh not ready)"
• Recent runs: !gh -R patrickjaja/claude-desktop-extra run list --workflow=build-and-release.yml --limit 3 2>/dev/null || echo "(gh not ready)"

Versioning semantics (format: {upstream}-{pkgrel})

• New upstream version (.upstream-version was bumped by /update): pkgrel resets to 1 automatically. This is the plain non-force run.
• Re-release at the same upstream version: pkgrel auto-increments (CI counts existing releases). This needs force_rebuild=true. It does not matter whether the change was a patch (new patched payload) or packaging-only (launcher, .desktop, packaging scripts) - both simply bump pkgrel; the kind of change belongs in the CHANGELOG entry and the release notes, not in the version.
• pkgrel is never chosen by hand. CI computes it (counts existing releases) and, after publishing, stamps it into packaging/nix/package.nix alongside version and the tarball hash - Nix consumers fetch from the release's own immutable tag (v<upstream> for pkgrel 1, v<upstream>-<pkgrel> otherwise; assets are never overwritten, issue #214). The pkgrel/hash literals in package.nix are CI-managed; never edit them manually.

Steps

1. Resolve the last release tag (from the Last release context above; v<upstream> or v<upstream>-<pkgrel>).
2. Decide FORCE (skip if $ARGUMENTS says force or no-force - explicit wins):
   • If .upstream-version on HEAD differs from the upstream part of the last release tag → FORCE=false (new-upstream release, pkgrel resets to 1).
   • Else look at what changed: git fetch --tags origin then git diff --name-only <last-tag>..origin/master. Classify:
     • any patches/ or js/ file → payload update → FORCE=true
     • else any scripts/, packaging/, PKGBUILD.template, *.install, flake.nix, .github/workflows/ file → packaging-only update → FORCE=true
     • else (docs/site/skills/CHANGELOG/baseline only) → STOP: nothing shippable changed; tell the user a release would publish identical packages and ask if they really want /deploy force.
3. Print a one-line plan including the classification, e.g. "Triggering build-and-release.yml on master (force_rebuild=true - packaging-only update, pkgrel will bump)". Mention the classification so the CHANGELOG/release notes wording can say "payload update" vs "packaging-only".
4. Fire it (no interactive confirmation - the user already typed /deploy):

   gh -R patrickjaja/claude-desktop-extra workflow run build-and-release.yml -f force_rebuild=<FORCE>
   

5. Wait ~3s, then resolve the run and report its URL:

   gh -R patrickjaja/claude-desktop-extra run list --workflow=build-and-release.yml --limit 1 \
     --json databaseId,url,status,event,createdAt
   

   Report the run URL and status. Offer: "Watch with gh -R patrickjaja/claude-desktop-extra run watch <id>".

Notes

• Do NOT bump versions or edit files here - this only triggers the pipeline. Version/patch work belongs in /update.
• If the diff shows BOTH a new .upstream-version and other changes, the non-force new-upstream run covers everything (the release builds from the committed tree).
• If gh workflow run errors with "Workflow does not have 'workflow_dispatch'" it's a permissions/branch issue - confirm the workflow file on master still declares workflow_dispatch.