ci: downloadable releases + TBD pipeline - #1
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add a Download section to README.md pointing users at the sdist/wheel tarballs attached to GitHub Releases (rolling `latest` vs stable tags), and a Releases (TBD) section to CONTRIBUTING.md describing the trunk-based tagging flow that drives release.yml.
…, least-privilege) and tidy cliff config
agarat
added a commit
that referenced
this pull request
Jul 15, 2026
ci: downloadable releases + TBD pipeline
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 downloadable releases and a CI pipeline for openpodgo, following Trunk-Based Development. Every push to
mainpublishes a rollinglatestpre-release; everyvX.Y.Ztag publishes a permanent stable release. Both attach an sdist + wheel and auto-generated changelog notes. No PyPI — the tarball from the Release is the distribution channel.Changes
pyproject.toml): version derived from git viasetuptools-scm(tagvX.Y.Z→X.Y.Z; no tag → a dev version). No more hand-editing.tests.yml): the matrix (3.10/3.11/3.12, offline, Qt offscreen) is nowworkflow_call.ci.ymlruns it on PRs only;release.ymlruns it as a gate onmain/tags — no double runs.release.yml):test → build → release. Builds sdist+wheel, generates notes withgit-cliff, and publishes to the correct channel by ref type (branchmain→ rollinglatest, prerelease; tagv*→ permanent stable). Least-privilege permissions (contents: writeonly on the publish job), aconcurrencygroup, the third-party publish action pinned to a full SHA (softprops/action-gh-release@v2.6.2), andtarget_commitishso thelatesttag advances to the pushed commit.cliff.toml): release notes generated from commit messages, grouped by the repo's scope prefixes. NoCHANGELOG.mdcommitted to the repo.READMEgains a## Downloadsection (install from the Release tarball);CONTRIBUTINGgains a## Releasesrunbook (how versions are derived and how to cut a stable).Verification
pytest: 341 passed, 3 skipped.actionlinton all three workflows: 0 findings.python -m buildproduces an installable sdist+wheel with a git-derived version;git-cliffproduces non-empty grouped notes.latesttag moves to the pushed commit and that--currenton the first stable tag yields the expected range.🤖 Generated with Claude Code