Skip to content

chore(ci): update workflow to use astral-sh/setup-uv@v6 with Python version#8508

Merged
ogabrielluiz merged 1 commit into
mainfrom
fix-ruff-ci
Jun 12, 2025
Merged

chore(ci): update workflow to use astral-sh/setup-uv@v6 with Python version#8508
ogabrielluiz merged 1 commit into
mainfrom
fix-ruff-ci

Conversation

@ogabrielluiz
Copy link
Copy Markdown
Contributor

@ogabrielluiz ogabrielluiz commented Jun 12, 2025

Summary by CodeRabbit

  • Chores
    • Updated workflow to use a specific Python version and improved environment setup with enhanced caching and configuration options.

…rkflow

- Changed Python version to 3.13 for better compatibility.
- Replaced local setup-uv action with astral-sh/setup-uv@v6 for improved reliability.
- Enabled caching with specific configurations to enhance build performance.
@dosubot dosubot Bot added the size:S This PR changes 10-29 lines, ignoring generated files. label Jun 12, 2025
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 12, 2025

Walkthrough

The workflow configuration was updated to switch from a locally defined setup action to the external astral-sh/setup-uv@v6 action, with explicit caching and Python version parameters. The environment variable was changed from a Poetry version to a Python version, and related configuration steps were updated accordingly.

Changes

File(s) Change Summary
.github/workflows/py_autofix.yml Replaced local setup-uv action with external astral-sh/setup-uv@v6, updated environment variables, and added cache-related parameters.

Sequence Diagram(s)

sequenceDiagram
    participant GitHub Actions
    participant astral-sh/setup-uv
    participant Python Environment

    GitHub Actions->>astral-sh/setup-uv: Setup environment (with cache, Python version)
    astral-sh/setup-uv->>Python Environment: Install Python 3.13, manage uv.lock caching
    GitHub Actions->>Python Environment: Run lint/update-starter-projects jobs
Loading

Possibly related PRs

Suggested labels

size:L, lgtm, ignore-for-release

Suggested reviewers

  • jordanrfrazier

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai Bot changed the title @coderabbitai chore(ci): update workflow to use astral-sh/setup-uv@v6 with Python version Jun 12, 2025
@ogabrielluiz ogabrielluiz merged commit 34c55f1 into main Jun 12, 2025
9 of 12 checks passed
@ogabrielluiz ogabrielluiz deleted the fix-ruff-ci branch June 12, 2025 12:30
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (1)
.github/workflows/py_autofix.yml (1)

34-39: Duplicate setup block detected
This block is the same as lines 17–22. See the earlier comment for suggestions on removing duplication.

🧹 Nitpick comments (1)
.github/workflows/py_autofix.yml (1)

17-22: DRY up duplicated setup steps
The astral-sh/setup-uv@v6 invocation (with cache config and python-version) is identical in multiple jobs. Consider extracting this into a reusable workflow, composite action, or YAML anchor to avoid duplication and ease maintenance.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 810a115 and 1d3f9f3.

📒 Files selected for processing (1)
  • .github/workflows/py_autofix.yml (3 hunks)
🔇 Additional comments (1)
.github/workflows/py_autofix.yml (1)

7-7:

Details

❓ Verification inconclusive

Verify Python version support
Python 3.13 is not yet officially available on GitHub runners by default. Confirm that astral-sh/setup-uv@v6 supports this version or adjust to a supported one (e.g., 3.12).


🏁 Script executed:

#!/bin/bash
set -e

echo "## GitHub-hosted runner Python versions (Ubuntu22-04):"
curl -s https://raw.githubusercontent.com/actions/virtual-environments/main/images/linux/Ubuntu22-04-Readme.md \
  | grep -A3 -i '^## Python'

echo
echo "## setup-uv v6 README excerpts for Python support:"
curl -s https://raw.githubusercontent.com/astral-sh/setup-uv/v6/README.md \
  | grep -i -A3 'python'

Length of output: 267


Verify Python version support
I was unable to confirm that Python 3.13 is available on GitHub-hosted runners (Ubuntu 22.04) or supported by astral-sh/setup-uv@v6. Please verify manually or switch to a known supported version (e.g., 3.12).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ignore-for-release size:S This PR changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant