ci(desktop): allow force building canary release

[Kitenite]

Summary

• Add a force_build input flag to the canary release workflow so manual dispatches can bypass change detection
• Update release:canary script to always pass force_build=true, ensuring manual triggers always build

Changes

• .github/workflows/release-desktop-canary.yml: Add force_build boolean input to workflow_dispatch, wrap change detection in a conditional that skips it when force is enabled
• package.json: Update release:canary script to pass -f force_build=true

Test Plan

• Trigger bun run release:canary and verify workflow starts without requiring new commits
• Verify scheduled runs still skip when no changes are detected (force_build defaults to false)

Summary by CodeRabbit

Release Notes

• Chores
  • Enhanced the canary build release process to support manually forcing builds, providing greater flexibility in triggering releases independent of code changes.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The changes add a force_build workflow dispatch input to the release-desktop-canary workflow that bypasses change detection when triggered manually. The package.json release:canary script is updated to automatically pass force_build=true when invoking the workflow.

Changes

Cohort / File(s)	Summary
GitHub Actions Canary Workflow .github/workflows/release-desktop-canary.yml	Adds force_build boolean workflow_dispatch input (default false). Refactors change-detection logic: if force_build is true, skip change detection and build; otherwise, preserve original flow with conditional checks for LAST_CANARY_SHA.
NPM Release Script package.json	Updates release:canary script to pass -f force_build=true flag to the workflow invocation, triggering automatic canary builds.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• feat(desktop): output run URL after triggering canary release #743: Modifies the same release:canary script in package.json to output the run URL.
• chore: add release:canary script #738: Updates the release:canary workflow invocation and GitHub Actions workflow logic in a prior iteration.
• feat(desktop): add canary build workflow for internal testing #721: Introduces the original release-desktop-canary.yml workflow that is being extended here.

Poem

🐰 A force to build, when needed most,
No need to check what changed the post,
With workflow dispatch, we bypass the test,
The canary sings its feathered best! ✨

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch kitenite/allow-release-canary-with-flag

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

🚀 Preview Deployment

🔗 Preview Links

Service	Status	Link
Database (Neon)	✅	View Branch
Electric (Fly.io)	✅	View App
Streams (Fly.io)	✅	View App
API (Vercel)	❌	Failed to deploy
Web (Vercel)	❌	Failed to deploy
Marketing (Vercel)	❌	Failed to deploy
Admin (Vercel)	❌	Failed to deploy
Docs (Vercel)	❌	Failed to deploy

---

Preview updates automatically with new commits