Automatically tag and release new versions on merge to main - #114
Open
huppd wants to merge 1 commit into
Open
Conversation
huppd
changed the title
huppd
marked this pull request as ready for review
August 7, 2026 08:18
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.
Previously, finishing a release required manually creating and pushing a git tag after the release PR was merged. This adds CI automation for that step:
New tag-release.yml workflow: triggers on push to main when pyproject.toml changes. If the version's vX.Y tag doesn't already exist, it creates and pushes the tag, publishes a GitHub Release with auto-generated notes, and explicitly dispatches the Docker build workflow for that tag.
deploy-container-for-release.yml: added a workflow_dispatch trigger so it can be invoked directly (tags pushed via the default GITHUB_TOKEN don't trigger other workflows, so this dispatch is needed rather than relying on the tag-push trigger alone).
README / scripts/release.sh: updated to reflect that tagging and releasing after merge is now automatic instead of a manual step.
Testing
YAML validated locally; not yet exercised end-to-end on GitHub Actions (needs a real merge to main with a version bump).
This PR were developed with AI assistance (Claude Code). Please review accordingly rather than assuming sole human authorship.