ci: extract publish workflow for manual releases

[FBumann]

Summary

• Extract publish job into separate publish.yml with manual workflow_dispatch trigger
• Allows ad-hoc releases (e.g. pre-releases from feature branches) by specifying a tag
• release.yml calls publish.yml via workflow_call on release-please releases

Test plan

• Manually trigger publish.yml with a tag from Actions tab
• Verify release-please flow still triggers publish on release creation

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Refactored the release automation to use a centralized publishing workflow, improving the consistency and maintainability of the package publication process.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

This pull request refactors GitHub Actions workflows by extracting PyPI publishing logic into a new reusable workflow file and updating the release workflow to delegate publishing to it instead of performing the steps inline.

Changes

Cohort / File(s)	Summary
New Publish Workflow .github/workflows/publish.yml	New reusable workflow for publishing to PyPI. Accepts tag input, checks out repository at specified tag, sets up uv and Python 3.12, builds package via uv build, and publishes to PyPI using pypa/gh-action-pypi-publish.
Release Workflow Refactoring .github/workflows/release.yml	Removed inline PyPI publishing steps from publish job and replaced with call to reusable workflow ./.github/workflows/publish.yml, passing release tag as input. Eliminates redundant job metadata (runner, timeout, environment configuration).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• ci: release please #26: Modifies the publish job in the release workflow to alter release and publishing behavior.
• ci: release-please.yml Now handles release creation AND PyPI publishing #34: Also refactors GitHub Actions for PyPI publishing and updates the release workflow structure.

Poem

🐰 From tangled steps we hop away,
A shiny workflow leads the way,
Reusable and clean, oh what a feat!
Now release and publish both compete,
Making CI pipelines sweet! 🐾

🚥 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 directly and clearly summarizes the main change: extracting the publish job into a separate, reusable GitHub Actions workflow.
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/add-publish-workflow

---

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.}