You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🤖 Add release workflow for automated binary publishing (#168)
## Summary
Adds automated release workflow that builds and publishes macOS and
Linux binaries when a GitHub release is published.
## Release Process
1. **Bump version** in (e.g., → )
2. **Commit and push** the version change to main
3. **Create a draft release** on GitHub with a tag (e.g., ) and write
release notes
4. **Publish the draft release** → triggers the workflow
5. **Wait for builds** (~10-15 minutes) - binaries are automatically
attached to the release
## Changes
- **** - New workflow triggered on `release: published`
- Builds macOS (x64 + arm64 DMGs)
- Builds Linux (AppImage)
- Uses `--publish always` to attach artifacts to GitHub release
- **** - Configure electron-builder to publish to GitHub releases
- **** - Document release process and workflow maintenance
## DRY Approach
The release workflow reuses the same build setup as :
- Same dependency installation steps
- Same build process
- Same code signing configuration
**Key difference:** uses for PR verification, while uses with to attach
binaries to releases.
## Testing
This can be tested by:
1. Merging this PR
2. Creating a test release (can be deleted after)
3. Verifying binaries are attached after workflow completes
_Generated with `cmux`_
0 commit comments