ci: auto-tag on version bump merge#11
Closed
nullhack wants to merge 18 commits into
Closed
Conversation
…erates bee-themed features directory
…es --beehave-sample
- Catch SystemExit from run_hatch() in pytest_configure and call pytest.exit(str(exc), returncode=1) for a clean exit instead of INTERNALERROR - Fix plugin_test.py mock so getoption returns False, preventing hatch branch from triggering and silently blocking 3 tests - Rewrite test_example_hatch_5e6f7a8b to use pytest.main() at CLI boundary, capturing stderr and asserting returncode==1 + conflicting path in output - Rewrite test_example_hatch_3c4d5e6f to use pytest.main() with stdout capture, asserting each written .feature relative path appears in output
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.
What
Adds
.github/workflows/tag-release.yml— a workflow that fires on every push tomainwhenpyproject.tomlchanges. It reads theversionfield and creates tagv{version}at the merge commit if it doesn't already exist.Why
Previously the release agent called
gh release createbefore the version bump PR was merged, causing the tag to land on the wrong commit (same SHA as the previous release). This made the PyPI publish build an identical wheel and reject it with400 File already exists.How it fits the release flow
No manual tag creation needed. The git-release skill is updated accordingly.