Skip to content

Conversation

@frontmesh
Copy link
Owner

Problem

Currently, when pushing to main, the workflow:

  1. Creates a tag (e.g., v0.1.0) ✅
  2. Does NOT build and create a GitHub Release

This means releases only exist as tags, not as actual GitHub Releases with compiled binaries.

Solution

Add a workflow_dispatch trigger in the auto-release job after creating the tag. This causes:

  1. Tag is created and pushed
  2. Workflow is triggered on the new tag
  3. Tests run on all platforms (Ubuntu, macOS, Windows)
  4. Build job compiles for all targets (Linux, macOS x86_64, macOS ARM64, Windows)
  5. Create-release job packages binaries and creates GitHub Release

Result

✅ GitHub Release is created with:

  • Compiled binaries for all platforms (.tar.gz for Unix, .exe for Windows)
  • Auto-generated release notes
  • Easy download from Releases page

Testing

Next version bump will trigger this flow automatically.
Manual testing: Push a version bump to main to see the workflow in action.

- Add workflow_dispatch trigger in auto-release job after tag creation
- This causes the workflow to run on the newly created tag
- Build job will compile for all platforms
- Create-release job will package binaries and create GitHub Release
- Previously: only tag was created
- Now: tag + GitHub Release with all compiled binaries
@frontmesh frontmesh merged commit e5c8a4b into main Nov 27, 2025
17 checks passed
@frontmesh frontmesh deleted the feature/fix-release-workflow branch November 27, 2025 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants