fix(ci): switch release workflow to tag-based triggering#5
Merged
Conversation
Replaces semantic-release automation with a straightforward tag-push trigger (v*). Version bumps happen via a PR; tagging main triggers build → PyPI publish → GitHub Release → Homebrew bump. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces the semantic-release automation with a simple tag-push trigger (
v*).New flow:
pyproject.toml+__init__.pyvia a PR → mergegit tag vX.Y.Z && git push origin vX.Y.Z→ triggers this workflowWhy: Semantic-release requires direct push to
mainfor its version-bump commit, which conflicts with branch protection on personal accounts (no bypass actors in classic rules or rulesets). Tag-based is simpler and works cleanly.🤖 Generated with Claude Code