feat: tag commit with version after PyPI publish#34
Conversation
Creates and pushes a git tag (e.g. v0.0.8) after the version bump commit so each published release is traceable in git history. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7e8e68ea3f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| git commit -m "chore: bump version to ${{ steps.bump.outputs.version }} [skip ci]" | ||
| git push | ||
|
|
||
| - name: Tag Version |
There was a problem hiding this comment.
This step runs unconditionally, so a workflow_dispatch run with inputs.target == 'test' will still create and push a v... git tag even though only TestPyPI was used. That makes test-only publishes look like official releases in git history and can interfere with downstream release practices that rely on tags representing production artifacts; the tag step should be gated with the same production condition used by Publish to PyPI.
Useful? React with 👍 / 👎.
1 participant
Summary
Tag Versionstep topypi_publish.ymlthat runs after the version bump commit is pushedv0.0.8) so each published release is traceable in git historyTest plan
workflow_dispatchagainst TestPyPIv0.0.x) appears in the repository after the run🤖 Generated with Claude Code