* feat: implement canary channel publishing for automatic main branch releases
Phase 1 of canary channel implementation - enables automatic publishing of canary builds:
**Infrastructure Changes:**
- Modified build.yml workflow to publish canary releases on main branch pushes
- Added canary:mac and canary:linux npm scripts that use --publish always
- Updated permissions to contents: write for release publishing
**Version Management:**
- Created prepare-canary.js script to generate unique canary versions (e.g., 0.1.17-canary.b329a36)
- Created restore-version.js script to restore original package.json after build
- Enhanced inject-build-info.js to detect and mark canary builds
**Release Strategy:**
- Canary builds now automatically create/update GitHub releases with downloadable artifacts
- Each canary version includes git commit hash for traceability
- Artifacts include DMG, AppImage, and electron-updater metadata files
- Extended artifact retention to 30 days for canary builds
**How it works:**
1. Push to main triggers GitHub Actions build workflow
2. Scripts create unique canary version number with git hash
3. electron-builder publishes to GitHub releases with --publish always
4. Version is restored to prevent git conflicts
5. Users can now download latest main branch builds from GitHub releases
Next: Phase 2 will add Settings UI toggle and electron-updater integration for automatic updates.
* test: temporarily enable canary workflow testing on canary-release branch
This allows testing the full GitHub Actions workflow without affecting main branch.
Will revert this change before final PR to only trigger on main branch pushes.
* revert: remove testing trigger, restore main-only canary publishing
Workflow now only triggers on main branch pushes as intended for production.
---------
Co-authored-by: Erick Shaffer <erick.shaffer@meraki.net>
Co-authored-by: Jordan Bentley <151466993+jordan-BAIC@users.noreply.github.com>