Skip to content

ci: add release workflow to publish artifacts on tag push#2

Merged
diranged merged 2 commits into
mainfrom
ci/release-workflow
Apr 7, 2026
Merged

ci: add release workflow to publish artifacts on tag push#2
diranged merged 2 commits into
mainfrom
ci/release-workflow

Conversation

@diranged

@diranged diranged commented Apr 7, 2026

Copy link
Copy Markdown
Owner

Summary

  • Adds .github/workflows/release.yml triggered on v* tag pushes
  • Builds CLI binary, .app bundle, and DMG on macos-15
  • Uses softprops/action-gh-release@v2 to find the draft release (from release-drafter), attach Graftery.dmg, Graftery.app.zip, and graftery CLI binary, then publish it

Release flow

  1. PRs merge to main → release-drafter maintains a draft release with changelog
  2. Push a tag (git tag v0.1.0 && git push --tags) → this workflow builds + attaches artifacts + publishes the draft

Test plan

  • Verify CI passes on this PR
  • After merge, push a test tag and confirm artifacts appear on the published release

🤖 Generated with Claude Code

When a version tag (v*) is pushed, this workflow builds the CLI binary,
.app bundle, and DMG, then attaches them to the draft release that
release-drafter has already prepared. Uses softprops/action-gh-release@v2
which automatically finds and publishes the existing draft.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
@diranged diranged changed the title Add release workflow to publish artifacts on tag push ci: add release workflow to publish artifacts on tag push Apr 7, 2026
Adds amannn/action-semantic-pull-request@v6 to enforce conventional
commit format on PR titles (feat:, fix:, ci:, docs:, etc.).

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
@diranged diranged merged commit f0057f6 into main Apr 7, 2026
3 checks passed
@diranged diranged deleted the ci/release-workflow branch April 7, 2026 01:50
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.

1 participant