CC @HarithaVattikuti / @aparnajyothi-y / @priya-kinthali

This should be merged: uv is becoming quite popular.

Please let me know if there's anything you need from the Astral team.

So exited for this!

Any update on this issue?

Rebased, rudimentary tests added.

I hope this really gets attention from one of the maintainers. The fact that CI pipelines are not even running without approval seems bit hostile to me. Let's hope is not by design...

Maybe @Jcambass or @HarithaVattikuti can give us a hand here?

FYI https://github.com/astral-sh/setup-uv is a GitHub Action developed as a drop-in replacement for actions/setup-python, having currently the following features:

• Install a version of uv and add it to PATH
• Cache the installed version of uv to speed up consecutive runs on self-hosted runners
• Register problem matchers for error output
• (Optional) Persist the uv's cache in the GitHub Actions Cache
• (Optional) Verify the checksum of the downloaded uv executable

FYI I talked to someone from GitHub at EuroPython and she said she'll try go ping the right people. No guarantees that it'll help but maybe we get lucky.

PS: Rebasing the PR so there are no conflicts might be a good idea, just in case it does get maintainer attention.

Hi @akx 👋, thank you for this contribution and thanks to everyone in the thread for your patience and interest.
After discussing internally, we've decided not to move forward with native cache: uv support in setup-python at this time.

As a workaround, if it's helpful, you can cache uv's cache directory using actions/cache, keyed on your lockfile:

- uses: actions/cache@v6
  with:
    path: ~/.cache/uv
    key: ${{ runner.os }}-uv-${{ hashFiles('**/uv.lock') }}
    restore-keys: |
      ${{ runner.os }}-uv-

We really appreciate the effort behind this PR and the community's engagement. While we won't be merging it now, it's something we're open to revisiting in the future. Thanks again for your understanding!