Skip to content

feat: tag commit with version after PyPI publish #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ghinks merged 1 commit into from
Mar 6, 2026
Merged

feat: tag commit with version after PyPI publish #34

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .github/workflows/pypi_publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,3 +64,8 @@ jobs:
git add pyproject.toml uv.lock
git commit -m "chore: bump version to ${{ steps.bump.outputs.version }} [skip ci]"
git push

- name: Tag Version
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Mar 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restrict version tag creation to production publishes

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 👍 / 👎.

run: |
git tag "v${{ steps.bump.outputs.version }}"
git push origin "v${{ steps.bump.outputs.version }}"
Loading