Add release automation: Makefile + CI and Trusted Publishing workflows#2
Open
aiand-atul wants to merge 1 commit into
Open
Add release automation: Makefile + CI and Trusted Publishing workflows#2aiand-atul wants to merge 1 commit into
aiand-atul wants to merge 1 commit into
Conversation
Codifies the release runbook from the 0.1.0 release: - Makefile targets (sync/test/lint/build/check/preflight/verify/tag/release), with the corrections learned during 0.1.0 (origin not upstream, Python >=3.10 verify venv, uv pip, import check outside the repo). - ci.yml: test/lint/build/check matrix on 3.10-3.13 for pushes and PRs. - publish.yml: tag-triggered build + PyPI Trusted Publishing (OIDC), no stored tokens; verifies the tag matches the pyproject version before publishing. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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.
Codifies the PyPI release process learned during the 0.1.0 release into repeatable tooling.
What's here
Makefile—sync/test/lint/build/check/preflight/verify/tag/release, plus a break-glass manualupload. Runmake helpfor the list..github/workflows/ci.yml— test/lint/build/check matrix on Python 3.10–3.13 for pushes and PRs..github/workflows/publish.yml— tag-triggered (v*) build + publish via PyPI Trusted Publishing (OIDC). No API tokens stored anywhere. Refuses to publish if the tag doesn't match thepyproject.tomlversion.Gotchas baked in (from the 0.1.0 release)
origin, notupstream.python3was 3.9.6).uv venvships nopip, so installs useuv pip./tmpso it loads the installed wheel, not the local./aiandsource tree.Verified locally
make help,make check, andmake verify VERSION=0.1.0(clean-room install from live PyPI) all pass.Required one-time setup (not in this PR)
Trusted Publishing needs a publisher configured on PyPI before
publish.ymlcan work:aiandlabs, Repositoryaiand-python, Workflowpublish.yml, EnvironmentpypipypiGitHub environment with required reviewers for an approval gate.Future release flow: bump version in the four places, then
make release VERSION=0.2.0.🤖 Generated with Claude Code