262 commits

Author	SHA1	Message	Date
Arthur Kim	f900ef9e57	setup-python/v5 exists, v6 don't exists. (#14533) ... ## Summary I suddenly found wrong documentation with setup-python in https://docs.astral.sh/uv/guides/integration/github/#setting-up-python. `setup-python/v5` exists, `setup-python/v6` don't exists. ## Test Plan nothing	2025-07-10 06:17:30 -05:00
Zanie Blue	812a3e7c34	Bump version to 0.7.20 (#14525)	2025-07-09 12:15:41 -05:00
Yu, Guangye	b1dc2b71a3	Add auto-detection for Intel GPUs (#14386) ... ## Summary This PR intends to enable `--torch-backend=auto` to detect Intel GPUs automatically: - On Linux, detection is performed using the `lspci` command via `Display controller` id. - On Windows, ~~detection is done via a `powershell` query to `Win32_VideoController`~~. Skip support for now—revisit once a better solution is available. Currently, Intel GPUs (XPU) do not rely on specific driver or toolkit versions to distribute different PyTorch wheels. ## Test Plan <!-- How was it tested? --> On Linux:  ~~On Windows: ~~ --------- Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2025-07-09 13:31:08 +00:00
Zanie Blue	dedced3265	Remove cache-dependency-glob examples for setup-uv (#14493) ... See https://github.com/astral-sh/uv/pull/13163#discussion_r2063244551	2025-07-07 15:06:23 -05:00
theirix	5c6d76ca8b	Update documentation for GHA to use v6 (#14490) ... ## Summary `astral-sh/setup-uv@v6` is the latest version of GitHub actions. ## Test Plan Documentation update	2025-07-07 14:04:45 -05:00
Zanie Blue	38ee6ec800	Bump version to 0.7.19 (#14431)	2025-07-02 21:19:52 +00:00
Zanie Blue	87e9ccfb92	Bump version to 0.7.18 (#14402)	2025-07-01 15:30:44 -05:00
Ondrej Profant	ae500c95d2	Docs: add instructions for publishing to JFrog's Artifactory (#14253) ... ## Summary Add instructions for publishing to JFrog's Artifactory into [documentation](https://docs.astral.sh/uv/guides/integration/alternative-indexes/). Related issues: https://github.com/astral-sh/uv/issues/9845 https://github.com/astral-sh/uv/issues/10193 ## Test Plan I ran the documentation locally and use npx prettier. --------- Co-authored-by: Ondrej Profant <ondrej.profant@datamole.ai> Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-06-30 13:58:55 +00:00
Charlie Marsh	41c218a89b	Bump version to 0.7.17 (#14347)	2025-06-29 09:58:33 -04:00
Zanie Blue	b6b7409d13	Bump version to 0.7.16 (#14334)	2025-06-27 16:46:36 -05:00
Daniel Vianna	4b348512c2	GCP Artifact Registry download URLs must have /simple path (#14251)	2025-06-25 17:35:41 +02:00
John Mumm	4ed9c5791b	Bump version to 0.7.15 (#14254)	2025-06-25 12:06:41 +02:00
Aria Desires	92de53f4eb	Bump version to 0.7.14 (#14218)	2025-06-23 12:48:51 -04:00
Charlie Marsh	a82c210cab	Add auto-detection for AMD GPUs (#14176) ... ## Summary Allows `--torch-backend=auto` to detect AMD GPUs. The approach is fairly well-documented inline, but I opted for `rocm_agent_enumerator` over (e.g.) `rocminfo` since it seems to be the recommended approach for scripting: https://rocm.docs.amd.com/projects/rocminfo/en/latest/how-to/use-rocm-agent-enumerator.html. Closes https://github.com/astral-sh/uv/issues/14086. ## Test Plan ``` root@rocm-jupyter-gpu-mi300x1-192gb-devcloud-atl1:~# ./uv-linux-libc-11fb582c5c046bae09766ceddd276dcc5bb41218/uv pip install torch --torch-backend=auto Resolved 11 packages in 251ms Prepared 2 packages in 6ms Installed 11 packages in 257ms + filelock==3.18.0 + fsspec==2025.5.1 + jinja2==3.1.6 + markupsafe==3.0.2 + mpmath==1.3.0 + networkx==3.5 + pytorch-triton-rocm==3.3.1 + setuptools==80.9.0 + sympy==1.14.0 + torch==2.7.1+rocm6.3 + typing-extensions==4.14.0 ``` --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-06-21 15:21:06 +00:00
Lucas Vittor	563e9495ba	Replace cuda124 with cuda128 (#14168) ... ## Summary <!-- What's the purpose of the change? What does it do, and why? --> Replace wrong `cuda124` version to the correct `cuda128` version in torch docs ## Test Plan <!-- How was it tested? -->	2025-06-20 16:05:17 -04:00
Charlie Marsh	6c096246d8	Remove preview label from --torch-backend (#14119) ... This is now used in enough places that I'm comfortable committing to maintaining it under our versioning policy. Closes #14091.	2025-06-17 16:49:00 -04:00
FishAlchemist	d653fbb133	doc: Sync PyTorch integration index for CUDA and ROCm versions from PyTorch website. (#14100) ... ## Summary Just to sync the documentation with PyTorch's officially recommended installation method.  **Change:** * CUDA 12.1 to CUDA 12.6 * CUDA 12.4 to CUDA 12.8 * ROCm 6.2 to ROCm 6.3 ## Test Plan Run doc server in local. Result: <details><summary>CUDA 12.6</summary> <p>   </p> </details> <details><summary>CUDA 12.8</summary> <p>   </p> </details> <details><summary>ROCm6</summary> <p>   </p> </details>	2025-06-17 09:55:03 -04:00
Zanie Blue	62ed17b230	Bump version to 0.7.13 (#14002)	2025-06-12 14:33:31 -05:00
Lan, Jian	90a7208a73	Fix and improve docs (#13620) ... <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary I follow the advices from the IDE spell checker and grammar checker, fix some typos, and improve the docs.	2025-06-10 13:15:38 -05:00
Karim Abou Zeid	5dae9ac5f2	Update referenced CUDA version in pytorch.md (#13899) ... ## Summary torch 2.7 by default targets CUDA 12.6	2025-06-08 20:21:07 -04:00
Zanie Blue	dc3fd46472	Bump version to 0.7.12 (#13892)	2025-06-06 19:42:06 +00:00
Jack O'Connor	94ed6f880f	update Git and GitHub Actions docs to mention gh auth login (#13850)	2025-06-05 20:44:59 +00:00
Zanie Blue	262ca73965	Remove the configuration section in favor of concepts / reference (#13842) ... Extends https://github.com/astral-sh/uv/pull/13841 — I'll drop that commit later after that pull request merges but it's small. I find the split into a "Configuration" section awkward and don't think it's helping us. Everything moved into the "Concepts" section, except the "Environment variables" page which definitely belongs in the reference and the "Installer" page which is fairly niche and seems better in the reference. Before / After <img src="https://github.com/user-attachments/assets/80d8304b-17da-4900-a5f4-c3ccac96fcc5" width="400">	2025-06-05 17:09:49 +00:00
Jack O'Connor	90a4416ab8	Bump version to 0.7.11 (#13844)	2025-06-04 12:35:56 -07:00
Zanie Blue	1e5120e15c	Bump version to 0.7.10 (#13821)	2025-06-03 11:07:21 -05:00
Zanie Blue	13a86a23b3	Bump version to 0.7.9 (#13739)	2025-05-30 14:30:37 -05:00
Zanie Blue	90a21ae46a	Add example of enabling Dependabot (#13692) ... Follows https://github.com/astral-sh/uv/pull/13690 Tested in https://github.com/astral-sh/packse/blob/main/.github/dependabot.yml	2025-05-28 11:10:14 +02:00
Akshay Agrawal	20cfc93c58	docs: integration with marimo guide (#13691) ... <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary This change adds a new integration guide, on using uv with marimo notebooks. It is similar to but simpler than the existing Jupyter guide, since marimo stores notebooks as Python files and also integrates tightly with uv for package management. The guide showcases four ways of using uv with marimo: 1. marimo as a standalone tool (`uvx`) 2. managing inline script metadata (an alternative to Jupyter kernels, marimo has no concept of kernels) 3. in project environments 4. in non-project environments ## Test Plan N/A as this is a docs-only change. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-05-27 18:43:43 -05:00
konsti	95c1463965	Update dependabot support status (#13690) ... Following user reports and https://github.com/dependabot/dependabot-core/issues?q=state%3Aopen%20label%3A%22L%3A%20python%3Auv%22%20sort%3Areactions-%2B1-desc, we're updating the dependabot support as partial. See https://github.com/astral-sh/uv/issues/2512#issuecomment-2900063741	2025-05-27 16:55:12 -05:00
Eva Müller	df00189ec5	docs: Explicitly specify to add a new repo entry to the repos list item in the .pre-commit-config.yaml (#10243) ... <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary When creating the `.pre-commit-config.yaml` from scratch, although following https://pre-commit.com/, it might be easy to overlook that the pre-commit repo examples need to be added below the `repos` list item to get a valid `yaml` file. Additionally, updated the version of the first two examples. ## Test Plan I followed the `CONTRIBUTING.md` and the result looked fine. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-05-27 16:25:23 +00:00
Arne Küderle	f657359729	Quote versions variables in GitLab documentation ... ## Summary Fixes #13675 ## Test Plan New example was tested manually to verify that it works.	2025-05-27 08:43:30 -04:00
Aria Desires	0ddcc19055	Bump version to 0.7.8 (#13629)	2025-05-23 19:13:28 -04:00
Aria Desires	8580b4bd2d	Bump version to 0.7.7 (#13601)	2025-05-22 14:42:26 -04:00
Zanie Blue	7f3e94a091	Bump version to 0.7.6 (#13537) ... Co-authored-by: Aria Desires <aria.desires@gmail.com>	2025-05-19 19:46:11 -04:00
Reza Gharibi	d4e8df9b94	Fix PowerShell code blocks (#13511) ... <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary The PowerShell prompt is not `$`, so it is not detected as a `Generic.Prompt` token by Pygments lexers. Therefore, the JavaScript code does not strip the prompt when copying from PowerShell code blocks, such as [here](https://docs.astral.sh/uv/getting-started/installation/#__tabbed_5_2). Other places in the docs have removed the prompt completely to address this issue: * https://docs.astral.sh/uv/guides/projects/#__tabbed_1_2 * https://docs.astral.sh/uv/guides/integration/jupyter/#__tabbed_1_2 This PR updates the PowerShell prompt to `PS>` and changes the code fence language to `pwsh-session` to match the lexer name from [Pygments](https://pygments.org/docs/lexers/#pygments.lexers.shell.PowerShellSessionLexer). This allows the prompt to be correctly detected as a `Generic.Prompt` token and is stripped during copy. Related: https://github.com/astral-sh/uv/pull/12520	2025-05-17 21:06:48 -05:00
Charlie Marsh	9d1a14e1f9	Bump version to v0.7.5 (#13500)	2025-05-16 20:37:17 -04:00
Zanie Blue	6fbcd09b5a	Bump version to 0.7.4 (#13473)	2025-05-15 11:08:50 -05:00
samypr100	395039afd1	feat(docker): add 3.14 beta images to uv docker (#13390) ... ## Summary Now that Python 3.14 first beta is out, I think it's worth adding support for the official upstream RC images. Once 3.14 is released, we can remove the `-rc-` infix from the images we pull from. ## Test Plan Upstream images verified to be functional with uv.	2025-05-13 20:27:09 +02:00
Zanie Blue	3c413f74b9	Bump verison to 0.7.3 (#13337)	2025-05-07 14:37:22 -05:00
Zanie Blue	481d05d8df	Bump version to 0.7.2 (#13240)	2025-04-30 14:01:58 -05:00
konsti	90f46f89a5	Bump version to 0.7.1 (#13218) ... Revert fix handling of authentication when encountering redirects ([#13215](https://github.com/astral-sh/uv/pull/13215))	2025-04-30 11:41:55 +02:00
Zanie Blue	1e8e08def2	Bump version to 0.7.0 and write changelog (#13201) ... The changelog diff is deranged. Rendered at https://github.com/astral-sh/uv/blob/zb/changelog-07/CHANGELOG.md#070 --------- Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com> Co-authored-by: Brent Westbrook <36778786+ntBre@users.noreply.github.com>	2025-04-29 16:37:00 -05:00
Charlie Marsh	990c59ddb6	Add ROCm example to the PyTorch guide (#13200) ... ## Summary Closes https://github.com/astral-sh/uv/issues/13197#issuecomment-2839707240.	2025-04-29 15:13:13 -04:00
Charlie Marsh	241b013600	Upgrade PyTorch guide to CUDA 12.8 and PyTorch 2.7 (#13199)	2025-04-29 15:08:13 -04:00
Charlie Marsh	8414e9f3dd	Bump version to v0.6.17 (#13110)	2025-04-25 12:57:07 -05:00
Zanie Blue	d8ad9d3cd6	Bump verison to 0.6.16 (#13042) ... Includes #13041 Also reverts https://github.com/astral-sh/uv/pull/13036	2025-04-22 03:53:08 +00:00
Zanie Blue	e2f400adbe	Bump version to 0.6.15 (#13034) ... Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2025-04-22 00:03:33 +00:00
Deividas / Dunixas	df35919d5a	teeny gramatical error in docs (#12908) ... <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary <!-- What's the purpose of the change? What does it do, and why? --> Incorrect use of the indefinite article- 'an project' instead of 'a project' ## Test Plan <!-- How was it tested? --> Was not tested due to it being a small change to docs wording without change in formatting.	2025-04-15 16:13:51 -05:00
Charlie Marsh	039b3c5dda	Refine lack of musl distributions to ARM-only (#12825)	2025-04-10 16:35:41 -05:00
johnthagen	719bab307c	Replace --frozen with --locked in Docker integration guide (#12818) ... ## Summary Replace `--frozen` with `--locked` in Docker integration guide. `--locked` additionally validates that `uv.lock` is "fresh"/up to date, which will catch errors if the user accidentally updated `pyproject.toml` but did not run `uv lock` before building the container. This is probably a better/safer default to recommend to users to avoid surprising/incorrect behavior. ## References - External guides already recommend using `--locked` instead of `--frozen` - https://hynek.me/articles/docker-uv/ - @zanieb seemed to indicate they might agree that `--locked` would be better to avoid surprises - https://github.com/astral-sh/uv/issues/10793#issuecomment-2743956736 ## Test Plan Used `--locked` in `uv` Python projects using Docker and validated that it works as expected.	2025-04-10 15:47:48 -04:00