From 68d643400ac99acc706a06b54b2088be3e41d535 Mon Sep 17 00:00:00 2001 From: FBumann <117816358+FBumann@users.noreply.github.com> Date: Mon, 9 Mar 2026 14:41:21 +0100 Subject: [PATCH] docs: update release instructions in CONTRIBUTING.md Replace stale manual git-tag workflow with current release-please process. Co-Authored-By: Claude Opus 4.6 --- CONTRIBUTING.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 070224b..d429f75 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -42,11 +42,8 @@ uv run ruff format . ## Releases -Releases are automated via GitHub Actions. Version is determined from git tags via setuptools_scm. +Releases are fully automated via [Release Please](https://github.com/googleapis/release-please). -To create a release: - -1. Tag: `git tag v0.1.0` -2. Push: `git push && git push --tags` - -The CI will automatically publish to PyPI and deploy updated docs. +1. Merge PRs to `main` using [conventional commit](https://www.conventionalcommits.org/) prefixes (`feat:`, `fix:`, etc.) +2. Release Please automatically creates/updates a release PR with changelog and version bump +3. Merge the release PR to publish to PyPI and deploy updated docs