fix: use tag-based versioning to work with branch protection#4
Merged
Conversation
Main is protected and rejects direct pushes from CI. Switch from pushing version bump commits to main to tagging the current HEAD and pushing only the tag. Version is derived from the latest git tag instead of __init__.py, so it advances correctly across runs.
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
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.
Problem
CI fails on push to main with:
The
mainbranch is now protected. The workflow was committing a version bump and runninggit push origin main --tags, which is rejected.Fix
Switch to tag-based versioning — no push to
mainat all:git tag --sort=-creatordate) instead of__init__.py, so the version always advances correctly across runsgit push origin <tag>). Main is never touched.__init__.pyin the tagged commitTest Plan