Skip to content

fix: run the release workflow when a release is published - #6

Merged
hibeekaey merged 2 commits into
mainfrom
fix/release-on-publish
Aug 16, 2026
Merged

fix: run the release workflow when a release is published#6
hibeekaey merged 2 commits into
mainfrom
fix/release-on-publish

Conversation

@hibeekaey

Copy link
Copy Markdown
Owner

The workflow triggered on push: tags, so a release published from the Releases page against an existing tag would silently do nothing: no assets, no formula bump.

  • Trigger is now release: [published], reading the tag from the event payload
  • New guard fails the release when bin/agent's VERSION does not match the tag, so a mislabeled binary cannot reach the assets or the Homebrew formula
  • CONTRIBUTING documents the full flow: PR with the version bump and changelog entry, then publish the release from the Releases page

Bumps VERSION to 1.5.1 so this release exercises the new path end to end.

🤖 Generated with Claude Code

hibeekaey and others added 2 commits August 16, 2026 23:19
Keying on tag pushes skipped any release published against an existing
tag, which is the normal Releases-page flow. The workflow now triggers on
release:published, reads the tag from the event, and fails the release if
bin/agent does not declare the released version.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
A release can be published from a commit that bypassed the PR checks, so
revalidate rather than assume. Publishing the skill stays out: gh skill
publish only creates new tags, which would fork a second version line.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@hibeekaey
hibeekaey merged commit 3f4f82b into main Aug 16, 2026
3 checks passed
@hibeekaey
hibeekaey deleted the fix/release-on-publish branch August 16, 2026 22:23
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