ci: adopt blueprint release pipeline

[FBumann]

Summary

Adopt the python-project-blueprint release pipeline:

• release.yaml: release-please on push to main, calls publish on release creation
• publish.yaml: triggered by tag push (v*) or workflow_call — publishes to PyPI and creates GitHub Release for manual tag pushes (auto-detects prerelease from - in tag name)
• docs.yml: updated workflow_run trigger to fire after Publish

Release flows

Flow	How
Automated release	Push to main → release-please PR → merge → tag + publish
Manual release	git tag v0.1.0 && git push origin v0.1.0 → publish
Manual pre-release	git tag v0.1.0-rc.1 && git push origin v0.1.0-rc.1 → publish (marked as prerelease)

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

• Chores
  • Updated release and publishing workflows to automatically publish package on version tag pushes.
  • Simplified release process by refactoring GitHub Actions workflows.
  • GitHub releases are now created automatically with generated release notes.

[coderabbitai]

Warning

Rate limit exceeded

@FBumann has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 26 minutes and 23 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: fc81eb44-be06-483e-8ad0-1e6a44b35d04

📥 Commits

Reviewing files that changed from the base of the PR and between 8988bda and 4b0d151.

📒 Files selected for processing (7)

• .github/workflows/ci.yml
• .github/workflows/docs.yml
• .github/workflows/latest-deps.yml
• .github/workflows/pr-title.yml
• .github/workflows/publish.yaml
• .readthedocs.yaml
• pyproject.toml

📝 Walkthrough

Walkthrough

The release automation workflows are restructured by removing automatic release-please triggering and old publish workflows, introducing a new unified publish.yaml workflow triggered by tag pushes and workflow calls, and updating the docs workflow to trigger from this new "Publish" workflow.

Changes

Cohort / File(s)	Summary
Release Workflow Restructuring .github/workflows/release.yaml, .github/workflows/release-please.yml	Removed automatic release-please workflow and eliminated workflow_dispatch inputs (branch, prerelease) from release.yaml. Updated publish job permissions with contents: write and attestations: write, and changed reusable workflow reference to new .yaml format.
Publish Workflow Migration .github/workflows/publish.yaml, .github/workflows/publish.yml	New publish.yaml workflow added with triggers for tag pushes (v*) and workflow_call invocation. Supports both PyPI publishing and GitHub Release creation. Old publish.yml removed entirely.
Documentation Workflow Trigger .github/workflows/docs.yml	Narrowed workflow_run trigger to watch only the "Publish" workflow instead of multiple upstream workflows ("Release (Manual)", "Release Please").

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• ci: release-please.yml Now handles release creation AND PyPI publishing #34: Directly modifies release and publish GitHub Actions workflows in coordination with this PR's removal and restructuring of automation workflows.
• ci: release please #26: Removes release-please workflow configuration, overlapping with the deletion of .github/workflows/release-please.yml in this PR.
• fix: docs deployment #19: Modifies .github/workflows/docs.yml workflow triggers, changing how docs deployment is initiated in relation to release workflows.

Poem

🐰 A publish workflow hops into place,
Tag-triggered releases at a quickening pace,
Release-please departs, old publish takes flight,
Docs follow the new Publish workflow's light,
hop hop ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'ci: adopt blueprint release pipeline' directly and clearly summarizes the main change: adopting a new blueprint-based release pipeline by replacing the existing release workflows with new ones.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/blueprint

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/publish.yaml:
- Around line 44-59: Gate the github-release job on the publish job and add an
idempotence check: change the job to depend on the publish job (reference the
job name "publish") and only run when that job succeeded (use an if conditional
like checking needs.publish.result == 'success'); inside the step that creates
the release, add a pre-check for an existing release (e.g., call "gh release
view $TAG" and skip creation if it exists) and keep the existing prerelease
branching logic (the TAG hyphen check) when creating a new release so reruns
won’t fail if the release already exists.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c076614a-7274-4d5b-9492-1dbb8a5ba077

📥 Commits

Reviewing files that changed from the base of the PR and between a23df5c and 8988bda.

📒 Files selected for processing (5)

• .github/workflows/docs.yml
• .github/workflows/publish.yaml
• .github/workflows/publish.yml
• .github/workflows/release-please.yml
• .github/workflows/release.yaml

💤 Files with no reviewable changes (2)

• .github/workflows/publish.yml
• .github/workflows/release-please.yml