Skip to content

ci: add Release Please for automated versioning and releases#8

Merged
weklund merged 1 commit intomainfrom
ci/release-please
Apr 2, 2026
Merged

ci: add Release Please for automated versioning and releases#8
weklund merged 1 commit intomainfrom
ci/release-please

Conversation

@weklund
Copy link
Copy Markdown
Owner

@weklund weklund commented Apr 2, 2026

Summary

  • Adds Release Please GitHub Action that runs on every push to main
  • Reads conventional commit prefixes (fix: → patch, feat: → minor, feat!: → major) to compute the next semver
  • Opens/updates a release PR with changelog — merging it creates the tag + GitHub release, which triggers the existing publish.yml → PyPI pipeline
  • Uses simple release type (tag-only) since hatch-vcs derives the version from the git tag

Files added

  • .github/workflows/release-please.yml — the workflow
  • release-please-config.json — release type and pre-1.0 bump rules
  • .release-please-manifest.json — current version baseline (0.3.1)

Test plan

  • Merge this PR and verify the workflow runs on the push to main
  • Verify Release Please opens a release PR (will be empty/no-op if no new conventional commits land after this)
  • On next fix: or feat: merge, confirm the release PR updates with correct version and changelog

🤖 Generated with Claude Code

Conventional commits (fix:/feat:/feat!:) now drive semver bumps
automatically. On every push to main, Release Please opens or updates
a release PR with the computed version and changelog. Merging that PR
creates the git tag and GitHub release, which triggers the existing
publish.yml pipeline to push to PyPI.

Uses simple release type (tag-only) since hatch-vcs derives the
version from the git tag — no version files to keep in sync.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@weklund weklund merged commit a4ad044 into main Apr 2, 2026
1 check passed
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