fix(ci): use uv build instead of python -m build

[w7-mgfcode]

Summary

Fix package build step in cd-release workflow.

Problem

error: No virtual environment found; run `uv venv` to create an environment

Solution

Use uv build which handles venv creation internally.

🤖 Generated with Claude Code

Summary by Sourcery

CI:

• Simplify the cd-release workflow by removing an explicit build-dependency installation step and switching the package build step to use uv build.

Summary by CodeRabbit

• Chores
  • Optimized the build process with streamlined build tooling configuration.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Update the cd-release GitHub Actions workflow to build the package using uv build, which manages its own virtual environment, and remove the now-unnecessary explicit build dependency installation step.

Flow diagram for cd-release job with uv build

flowchart TD
  A["Start cd-release job"] --> B["Set up Python with uv python install"]
  B --> C["Build package with uv build"]
  C --> D["List dist/ directory contents"]
  D --> E["Upload release assets"]
  E --> F["End job"]

Loading

File-Level Changes

Change	Details	Files
Switch package build step in cd-release workflow from python -m build (with separate build dependency installation) to uv build, relying on uv to manage the environment and build tooling.	Remove explicit installation of the build package via uv pip install build in the release workflow. Change the package build command from python -m build to uv build in the release workflow. Keep the post-build ls -la dist/ step to verify build artifacts remain unchanged in behavior.	.github/workflows/cd-release.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

📝 Walkthrough

Walkthrough

The GitHub Actions CD release workflow has been simplified by replacing the python -m build command with uv build and removing the explicit build dependency installation step, consolidating the build process into a single UV-powered command.

Changes

Cohort / File(s)	Summary
CI/CD Workflow Update .github/workflows/cd-release.yml	Removed explicit build dependency installation (uv pip install build) and switched build command from python -m build to uv build

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A tool switch so neat, from Python to UV,
The build now runs swift, dependencies free,
One command replaces the old lengthy way,
The workflow hops forward to a faster day! ✨

🚥 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 specifically describes the main change: replacing 'python -m build' with 'uv build' in the CI workflow, which directly matches the changeset modifications.
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.}

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}