chore: remove redundant python setup in CI

[twangodev]

Summary by CodeRabbit

• Chores
  • Optimized CI workflows for consistency and maintainability.
  • Standardized Python version handling across jobs (matrix entries simplified to "3" and a project Python runtime set to 3.9).
  • Simplified version propagation to subsequent steps and adjusted coverage upload condition to match the new version handling.

[coderabbitai]

Walkthrough

Refactored GitHub Actions to centralize Python version provisioning in the astral-sh/setup-uv@v7 step; removed separate actions/setup-python steps in CI flows, added python-version to docs workflow's uv step, and added a .python-version file specifying 3.9.

Changes

Cohort / File(s)	Summary
CI workflow: consolidate Python setup \.github/workflows/python\.yml	Removed explicit actions/setup-python steps; moved Python version specification into astral-sh/setup-uv@v7 via with: python-version for lint/type-check, test (matrix), and integration jobs; normalized matrix entries from 3.x → 3.
Docs workflow: uv step python-version added \.github/workflows/docs\.yml	Added python-version: "3" to the astral-sh/setup-uv@v7 step; no other control-flow changes.
Repository runtime hint \.python-version	Added file containing 3.9 to indicate a preferred Python runtime version.

Sequence Diagram(s)

sequenceDiagram
  participant Dev as Developer/PR
  participant GH as GitHub Actions
  participant UV as astral-sh/setup-uv
  participant Py as actions/setup-python

  rect rgb(230,240,255)
    Note over GH,UV: New flow (after changes)
    Dev->>GH: Trigger workflow
    GH->>UV: Install uv (python-version: matrix or "3")
    UV-->>GH: Python runtime provided
    GH->>GH: Run lint/test/integration steps
  end

  rect rgb(255,240,230)
    Note over GH,Py: Old flow (before changes)
    Dev->>GH: Trigger workflow
    GH->>Py: actions/setup-python (per-job)
    Py-->>GH: Python runtime provided
    GH->>UV: Install uv (no python-version)
    UV-->>GH: uv installed
    GH->>GH: Run lint/test/integration steps
  end

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify matrix and per-job python-version values match intended runtimes (especially coverage/conditional checks).
• Confirm .python-version (3.9) aligns with matrix entries and repository requirements.
• Ensure astral-sh/setup-uv invocation propagates the python version to subsequent steps and doesn’t rely on prior actions/setup-python.

Poem

🐰 I nudged the setup, made it neat and spry,
uv now carries Python — no extra try.
A carrot for CI, a hop in the stream,
Cozy runtimes, and faster dream. ✨

Pre-merge checks and finishing touches

✅ 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 'chore: remove redundant python setup in CI' directly and accurately describes the main changes in the PR - removing explicit Python setup steps and consolidating Python version handling into the uv installation step across CI workflows.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/python-ci

---

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

[Copilot]

Pull Request Overview

This PR simplifies the CI workflow by consolidating Python installation into the setup-uv action, eliminating redundant actions/setup-python steps.

• Removed separate Python setup steps from three jobs (type-check, test, integration)
• Configured setup-uv to handle Python installation directly via the python-version parameter
• Maintained identical Python version specifications for each job

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
see 5 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

.python-version (1)

1-1: Local 3.9 pin vs CI’s generic Python 3

Pinning local development to 3.9 is fine, but CI is configured to use "3" (latest 3.x), so behavior may diverge as GitHub’s default advances. Consider either aligning this to the same major/minor as CI or documenting that local is pinned to 3.9 while CI floats on 3.x so contributors understand the intentional difference.

.github/workflows/docs.yml (1)

21-22: setup-uv Python provisioning looks correct; consider explicit version strategy

The with: python-version: "3" addition is syntactically correct and aligns this workflow with the new pattern of letting astral-sh/setup-uv manage Python, which matches the PR intent to avoid separate setup-python steps.

If you care about strict reproducibility, you might optionally:

• Pin a specific minor (e.g., "3.9" or "3.11") here, or
• Align this value with .python-version to avoid subtle differences between docs CI and local dev.

Not a blocker—current config is valid as-is.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f12b1f7 and 911a253.

📒 Files selected for processing (3)

• .github/workflows/docs.yml (1 hunks)
• .github/workflows/python.yml (3 hunks)
• .python-version (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/workflows/python.yml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Integration Tests
• GitHub Check: Integration Tests