chore: consolidate release workflow into single job

[hyunhee-jo]

Objective

The release workflow runs Python setup and checkout twice — once for the test job and once for the publish job. This wastes CI time on duplicate environment setup for every release.

Approach

Merge the two jobs (test → publish) into a single job that runs test → build → publish sequentially. Remove the environment: release setting which was not configured on PyPI trusted publisher.

Evidence

Compared before/after workflow structure:

Scenario	Before	After
Python setup calls	2 (test job + publish job)	1
Checkout calls	2	1
Test gate before publish	Yes (separate job needs)	Yes (sequential steps)
Environment setting	release (not configured)	Removed

Summary by CodeRabbit

• Chores
  • Streamlined the release workflow by consolidating test and publish steps into a unified process for improved efficiency.

[coderabbitai]

Walkthrough

The release workflow is restructured to consolidate test and publish operations into a single sequential job instead of separate dependent jobs. The build tooling setup is simplified by removing the pip upgrade step during installation.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/release.yml	Merged separate test and publish jobs into single release job with sequential steps. Removed duplicate checkout and Python setup. Simplified build tool installation from pip install --upgrade pip uv to pip install uv. Retained pytest execution, version update, build, and PyPI publish steps.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 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 clearly and concisely summarizes the main change: consolidating two separate workflow jobs (test and publish) into a single job to eliminate duplication.
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.}

---

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/release.yml:
- Line 14: The pipeline's job timeout is still set to "timeout-minutes: 10" but
the job now runs test, build and publish sequentially; increase the timeout to a
higher value (e.g., 30 or 60) by updating the "timeout-minutes" key in the
workflow (replace the "timeout-minutes: 10" entry) so the combined job won't be
cancelled under normal variance; pick a value appropriate for your longest
expected run time and CI provider limits.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 93a1612a-c3b9-4185-8810-e01af1f5583c

📥 Commits

Reviewing files that changed from the base of the PR and between cb85b3b and 130d653.

📒 Files selected for processing (1)

• .github/workflows/release.yml