ci: release automation — auto-bump version and create GitHub Release on merge to main#72
Merged
Merged
Conversation
On every push to main (excluding version bump commits), bumps the patch version in __init__.py, commits it, and creates a GitHub Release with a changelog built from commits since the last tag. The existing publish.yml and publish-vscode.yml workflows trigger on release published, so PyPI and VS Code Marketplace publishing continue to work without changes. Co-authored-by: Ona <no-reply@ona.com>
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/release.yml— a workflow that runs on every push tomainand:src/agent_trace/__init__.py0.32.0→0.32.1)mainvX.Y.Zwith that changelog as the bodyThe existing
publish.yml(PyPI) andpublish-vscode.yml(VS Code Marketplace) both trigger onrelease: published, so they continue to work without any changes.Why
Every subsequent PR in this batch (drift, dashboard --trend, optimize, Langfuse export) needs a release to ship. This workflow means merging a PR to
mainis sufficient — no manual tagging or release creation required.Guard against infinite loop
The workflow skips itself when the triggering commit message starts with
chore: bump version to, which is the exact message the workflow uses for its own commit.Checklist
GITHUB_TOKEN(no new secrets required)