357 commits

Author	SHA1	Message	Date
Zanie Blue	21fadbcc13	Bump version to 0.8.2 (#14832)	2025-07-22 19:39:53 +00:00
Zanie Blue	f0151f3a18	Bump version to 0.8.1 (#14818)	2025-07-22 11:36:20 -05:00
Ali Chaudry	7a56950bab	Update setup-uv docs for Github Actions integration guide (re-order python and uv setup) (#14741) ... I updated the Github Actions integration guide to run Github's `setup-python` before Astral's `setup-uv`, as `setup-uv`'s `activate-environment: true` doesn't work with the original ordering. There is a discussion about this behavior in the `setup-uv` repo [here](https://github.com/astral-sh/setup-uv/issues/479). <!-- 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 Update the documentation for the Github Actions integration. Caveat: I'm unsure if there are any other reasons where the original ordering (that is,`setup-uv` before `setup-python`) might be preferred. ## Test Plan Tested in a private Github Actions push, as documented in the aforementioned discussion on `setup-uv`'s repo. Confirmed that removing `source .venv/bin/activate` and replacing it with `activate-environment: true` now works in this ordering (but didn't work with the original ordering where `uv` installs before Github's `python`).	2025-07-21 14:48:47 -05:00
Zanie Blue	1a339b76e8	Add release notes and bump version for 0.8.0 (#14690) ... [Rendered](https://github.com/astral-sh/uv/blob/zb/release-notes/CHANGELOG.md)	2025-07-17 17:20:21 -05:00
Zanie Blue	0077f2357f	Stabilize addition of Python executables to the bin (#14626) ... Closes https://github.com/astral-sh/uv/issues/14296 As mentioned in #14681, this does not stabilize the `--default` behavior.	2025-07-17 17:20:21 -05:00
samypr100	35e2f67b5e	feat(docker): set default UV_TOOL_BIN_DIR on docker images (#13391) ... Closes #13057 Sets `UV_TOOL_BIN_DIR` to `/usr/local/bin` for all derived images to allow `uv tool install` to work out of the box. Note, when the default image user is overwritten (e.g. `USER <UID>`) by a less privileged one, an alternative writable location would now need to be set by downstream consumers to prevent issues, hence I'm labeling this as a breaking change for 0.8.x release. Relates to https://github.com/astral-sh/uv-docker-example/pull/55 Each image was tested to work with uv tool with `UV_TOOL_BIN_DIR` set to `/usr/local/bin` with the default root user and alternative non-root users to confirm breaking nature of the change.	2025-07-17 17:20:21 -05:00
Zanie Blue	78d6d1134a	Bump version to 0.7.22 (#14685)	2025-07-17 11:27:15 -05:00
Geoffrey Thomas	77c771c7f3	Bump version to 0.7.21 (#14611)	2025-07-14 14:01:28 -04:00
Aria Desires	042df4a7de	Expand the functionality of uv version --bump to support pre-releases (#13578) ... This adds `alpha`, `beta`, `rc`, `stable`, `post`, and `dev` modes to `uv version --bump`. The components that `--bump` accepts are ordered as follows: major > minor > patch > stable > alpha > beta > rc > post > dev Bumping a component "clears" all lesser component (`alpha`, `beta`, and `rc` all overwrite each other): * `--bump minor` on `1.2.3a4.post5.dev6` => `1.3.0` * `--bump alpha` on `1.2.3a4.post5.dev6` => `1.2.3a5` * `--bump dev ` on `1.2.3a4.post5.dev6` => `1.2.3a4.post5.dev7` In addition, `--bump` can now be repeated. The primary motivation of this is "bump stable version and also enter a prerelease", but it technically lets you express other things if you want them: * `--bump patch --bump alpha` on `1.2.3` => `1.2.4a1` ("bump patch version and go to alpha 1") * `--bump minor --bump patch` on `1.2.3` => `1.3.1` ("bump minor version and got to patch 1") * `--bump minor --bump minor` on `1.2.3` => `1.4.0` ("bump minor version twice") The `--bump` flags are sorted by their priority, so that you don't need to remember the priority yourself. This ordering is the only "useful" one that preserves every `--bump` you passed, so there's no concern about loss of expressiveness. For instance `--bump minor --bump major` would just be `--bump major` if we didn't sort, as the major bump clears the minor version. The ordering of `beta` after `alpha` means `--bump alpha --bump beta` will just result in beta 1; this is the one case where a bump request will effectively get overwritten. The `stable` mode "bumps to the next stable release", clearing the pre (`alpha`, `beta`, `rc`), `dev`, and `post` components from a version (`1.2.3a4.post5.dev6` => `1.2.3`). The choice to clear `post` here is a bit odd, in that `1.2.3.post4` => `1.2.3` is actually a version decrease, but I think this gives a more intuitive model (as preserving `post5` in the previous example is definitely wrong), and also post-releases are extremely obscure so probably no one will notice. In the cases where this behaviour isn't useful, you probably wanted to pass `--bump patch` or something anyway which *should* definitely clear the `post5` (putting it another way: the only cases where `--bump stable` has dubious behaviour is when you wanted it to do a noop, which, is a command you could have just not written at all). In all cases we preserve the "epoch" and "local" components of a version, so the `7!` and `+local` in `7!1.2.3+local` will never be modified by `--bump` (you can use the raw version set mode if you want to touch those). The preservation of `local` is another slightly odd choice, but it's a really obscure feature (so again it mostly won't come up) and when it's used it seems to mostly be used for referring to variant releases, in which case preserving it tends to be correct. Fixes #13223 --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-07-10 08:45:17 -05:00
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	c3f13d2505	Finish incomplete sentence in pip migration guide (#14432) ... Fixes https://github.com/astral-sh/uv/pull/12382#discussion_r2181237729	2025-07-03 01:02:17 +00:00
Zanie Blue	38ee6ec800	Bump version to 0.7.19 (#14431)	2025-07-02 21:19:52 +00:00
Zanie Blue	2f53ea5c5c	Add a migration guide from pip to uv projects (#12382) ... [Rendered](https://github.com/astral-sh/uv/blob/zb/pip-wip/docs/guides/migration/pip-to-project.md) --------- Co-authored-by: samypr100 <3933065+samypr100@users.noreply.github.com> Co-authored-by: Mathieu Kniewallner <mathieu.kniewallner@gmail.com> Co-authored-by: Aria Desires <aria.desires@gmail.com>	2025-07-02 12:25:19 -05: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
dmitry-bychkov	61265b0c14	Add a link to PyPI FAQ to clarify what per-project token is. (#14242) ... <!-- 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 link to PyPI FAQ about API tokens on the package publishing guide page. To me it wasn't clear what are meant in this section of the docs and it required a little bit of research. Adding explicit link might help beginners. <!-- What's the purpose of the change? What does it do, and why? --> Co-authored-by: Dmitry Bychkov <dbychkov@alarislabs.com>	2025-06-24 11:56:36 -04: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
John Mumm	e9d5780369	Support transparent Python patch version upgrades (#13954) ... > NOTE: The PRs that were merged into this feature branch have all been independently reviewed. But it's also useful to see all of the changes in their final form. I've added comments to significant changes throughout the PR to aid discussion. This PR introduces transparent Python version upgrades to uv, allowing for a smoother experience when upgrading to new patch versions. Previously, upgrading Python patch versions required manual updates to each virtual environment. Now, virtual environments can transparently upgrade to newer patch versions. Due to significant changes in how uv installs and executes managed Python executables, this functionality is initially available behind a `--preview` flag. Once an installation has been made upgradeable through `--preview`, subsequent operations (like `uv venv -p 3.10` or patch upgrades) will work without requiring the flag again. This is accomplished by checking for the existence of a minor version symlink directory (or junction on Windows). ### Features * New `uv python upgrade` command to upgrade installed Python versions to the latest available patch release: ``` # Upgrade specific minor version uv python upgrade 3.12 --preview # Upgrade all installed minor versions uv python upgrade --preview ``` * Transparent upgrades also occur when installing newer patch versions: ``` uv python install 3.10.8 --preview # Automatically upgrades existing 3.10 environments uv python install 3.10.18 ``` * Support for transparently upgradeable Python `bin` installations via `--preview` flag ``` uv python install 3.13 --preview # Automatically upgrades the `bin` installation if there is a newer patch version available uv python upgrade 3.13 --preview ``` * Virtual environments can still be tied to a patch version if desired (ignoring patch upgrades): ``` uv venv -p 3.10.8 ``` ### Implementation Transparent upgrades are implemented using: * Minor version symlink directories (Unix) or junctions (Windows) * On Windows, trampolines simulate paths with junctions * Symlink directory naming follows Python build standalone format: e.g., `cpython-3.10-macos-aarch64-none` * Upgrades are scoped to the minor version key (as represented in the naming format: implementation-minor version+variant-os-arch-libc) * If the context does not provide a patch version request and the interpreter is from a managed CPython installation, the `Interpreter` used by `uv python run` will use the full symlink directory executable path when available, enabling transparently upgradeable environments created with the `venv` module (`uv run python -m venv`) New types: * `PythonMinorVersionLink`: in a sense, the core type for this PR, this is a representation of a minor version symlink directory (or junction on Windows) that points to the highest installed managed CPython patch version for a minor version key. * `PythonInstallationMinorVersionKey`: provides a view into a `PythonInstallationKey` that excludes the patch and prerelease. This is used for grouping installations by minor version key (e.g., to find the highest available patch installation for that minor version key) and for minor version directory naming. ### Compatibility * Supports virtual environments created with: * `uv venv` * `uv run python -m venv` (using managed Python that was installed or upgraded with `--preview`) * Virtual environments created within these environments * Existing virtual environments from before these changes continue to work but aren't transparently upgradeable without being recreated * Supports both standard Python (`python3.10`) and freethreaded Python (`python3.10t`) * Support for transparently upgrades is currently only available for managed CPython installations Closes #7287 Closes #7325 Closes #7892 Closes #9031 Closes #12977 --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-06-20 16:17:13 +02:00
Jack O'Connor	cc8d5a9215	handle an existing shebang in uv init --script (#14141) ... Closes https://github.com/astral-sh/uv/issues/14085.	2025-06-19 14:47:22 -07: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
Abhishek Upadhye	efd4652faa	List .gitignore in project init files (#13855) ... Fixes https://github.com/astral-sh/uv/issues/13639 Just added a missing `.gitignore` file in the docs, so that there would be no confusion for readers referring it. Thank you!	2025-06-05 09:21:15 -05: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