Skip to content

docs: document the automated release pipeline - #62

Merged
mrwadams merged 1 commit into
mainfrom
docs/document-release-pipeline
Jul 21, 2026
Merged

docs: document the automated release pipeline#62
mrwadams merged 1 commit into
mainfrom
docs/document-release-pipeline

Conversation

@mrwadams

Copy link
Copy Markdown
Owner

Adds a Cutting a Release section to CLAUDE.md so future contributors (and agents) know how the automated pipeline works and how to trigger it.

Documents:

  • The release.yml flow: v*.*.* tag → verify → test → multi-arch Docker Hub push → GitHub Release
  • The correct steps to cut a release (bump pyproject.toml, land on main, then tag/push)
  • The verify gate (tag must match packaged version) and the strict 3-component semver requirement

Docs only — no code or workflow changes.

🤖 Generated with Claude Code

Add a "Cutting a Release" section to CLAUDE.md so agents know the automated
flow: bump pyproject.toml version, land on main, then push a v*.*.* tag to
trigger the multi-arch Docker Hub publish + GitHub Release. Note the verify
gate (tag must match packaged version) and the strict 3-component semver
requirement.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@mrwadams
mrwadams merged commit f8ebe1a into main Jul 21, 2026
7 checks passed
@mrwadams
mrwadams deleted the docs/document-release-pipeline branch July 21, 2026 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant