398 commits

Author	SHA1	Message	Date
Zanie Blue	ee2649feaa	Bump version to 0.9.4 (#16347)	2025-10-17 16:02:02 -05:00
Yu, Guangye	de9f299b80	Add auto-detection for Intel GPU on Windows (#16280) ... This PR enables `--torch-backend=auto` to automatically detect Intel GPUs. It follows up on [#14386](https://github.com/astral-sh/uv/pull/14386). On Windows, detection is implemented by querying the `Win32_VideoController` class via the [WMI crate](https://github.com/ohadravid/wmi-rs/tree/v0.16.0). Currently, Intel GPUs (XPU) do not depend on specific driver or toolkit versions to determine which PyTorch wheel to use.	2025-10-16 16:56:07 -04:00
Zanie Blue	9db7d38cf7	Bump version to 0.9.3 (#16305)	2025-10-14 18:19:49 -05:00
William Woodruff	141369ce73	Bump version to 0.9.2 (#16238) ... Co-authored-by: Geoffrey Thomas <geofft@ldpreload.com>	2025-10-10 14:20:14 -04:00
Zanie Blue	9887ef5bd7	Bump version to 0.9.1 (#16212) ... Archives the 0.8.x changelog too.	2025-10-09 18:28:59 +00:00
Zanie Blue	39b6886536	Bump version to 0.9.0 (#16161) ... Co-authored-by: konsti <konstin@mailbox.org>	2025-10-07 23:17:42 +00:00
samypr100	593678055f	Publish Python 3.14 Docker Images (#16150) ... ## Summary Tentative PR to drop the `-rc` suffix from the published images. Do not merge this yet until the formal release [upstream](https://hub.docker.com/_/python) :)	2025-10-07 18:10:07 -05:00
samypr100	2f7bb7e8ca	Promote trixie and alpine 3.22 as default tags (#15352) ... ## Summary Semi related to https://github.com/astral-sh/uv/issues/15270, except there's no removal. Makes Alpine 3.22 and debian trixie the default tags instead of removing bookworm and alpine 3.21 to minimize churn. ~~This PR is pending https://github.com/astral-sh/uv/pull/15351 merged first.~~ Merged ## Test Plan No functional changes made besides changing tag pointers.	2025-10-07 17:26:37 -05:00
Zanie Blue	252f887338	Bump version to 0.8.24 (#16146)	2025-10-07 03:03:01 +00:00
Kevin Neal	525ea78399	doc: fix example of bumping beta version without patch bump (#16132) ... <!-- 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? --> Fixes #16131 ## Summary Fix error in example documentation for bumping version. ## Test Plan I viewed the markdown on the branch in my fork. Looked good.	2025-10-06 11:16:01 +02:00
Zanie Blue	00d3aa3780	Bump version to 0.8.23 (#16119)	2025-10-04 12:46:01 -05:00
Zanie Blue	ade2bdbd2a	Bump version to 0.8.22 (#16005)	2025-09-23 14:43:48 -05:00
Charlie Marsh	f64da27450	Bump version to v0.8.21 (#16001)	2025-09-23 13:55:19 +00:00
Zanie Blue	3e6fd0b775	Bump version to 0.8.20 (#15998)	2025-09-22 22:34:27 +00:00
Zanie Blue	e9987b3b57	Tweak title for viewing version in project guide (#15964)	2025-09-22 08:56:06 -05:00
Zanie Blue	fc7c2f8b50	Bump version to 0.8.19 (#15953)	2025-09-19 14:34:41 -05:00
Zanie Blue	c4c47814a8	Bump version to 0.8.18 (#15920)	2025-09-17 16:13:41 -05:00
konsti	759eab837a	Add GitHub Actions to PyPI trusted publishing example (#15753) ... Add a complete example for the most common publishing workflow, GitHub Actions to PyPI, with screenshots for settings and a standalone companion repo. Closes #14398	2025-09-17 19:25:17 +02:00
Christian Clauss	fb71b079d5	guides/integration/github.md: Upgrade checkout action to v5 (#15887) ... <!-- 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? --> Upgrade checkout action to v5 -- https://github.com/actions/checkout/releases ## Test Plan <!-- How was it tested? -->	2025-09-16 07:53:00 +00:00
James Bourbeau	0b8117a9f7	Add Coiled integration doc page (#14430) ... This PR adds a new integrations doc page for using uv with [Coiled](https://coiled.io/). It's a slightly adapted version of this blog post https://docs.coiled.io/blog/uv-coiled-cloud-scripts.html Side note: it's been really pleasant using uv and Coiled together recently cc @zanieb for visibility --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-09-12 12:24:32 +00:00
Zanie Blue	7789f5b217	Bump version to 0.8.17 (#15776)	2025-09-10 14:59:48 -05:00
Charlie Marsh	2de677b0d3	Bump version to v0.8.16 (#15761) ... Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-09-09 21:41:56 -04:00
Antony Kellermann	b68161f0ca	adds docs for docker caching for managed python (#15689) ... <!-- 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 Closes #15586	2025-09-04 13:50:22 -05:00
Charlie Marsh	70cb0df7c2	Bump version to v0.8.15 (#15648)	2025-09-03 02:10:58 +00:00
Zanie Blue	af856fb883	Bump version to 0.8.14 (#15576)	2025-08-28 21:25:02 +00:00
Zanie Blue	bf189c5414	Split the "Authentication" page into sections (#15575) ... In preparation for more content for #15570	2025-08-28 15:45:31 -05:00
KotlinIsland	f231d0f2a5	Fix github doc highlight lines (#15443) ... <!-- 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 noticed some of the line highlights are wrong in the docs ## Test Plan visual verification	2025-08-22 11:28:41 -05:00
Zanie Blue	ede75fe628	Bump version to 0.8.13 (#15423)	2025-08-21 13:52:39 -05:00
samypr100	5b088e9430	chore: add trixie base images and alpine 3.22 support (#15351) ... ## Summary Follow up to https://github.com/astral-sh/uv/pull/15269#issuecomment-3194000772 Enables the following additional images to be published * buildpack-deps:trixie * debian:trixie-slim * alpine:3.22 ## Test Plan Existing Tests. The newly added images were checked manually.	2025-08-18 17:55:42 -05:00
Zanie Blue	f784c334cf	Bump version to 0.8.12 (#15364)	2025-08-18 22:14:51 +00:00
Zanie Blue	f892276ac8	Bump version to 0.8.11 (#15287)	2025-08-14 14:21:10 -05:00
smeng9	d8d4f02e5e	Add Debian 13 trixie to published Docker images (#15269) ... Closes https://github.com/astral-sh/uv/issues/15230 --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-08-14 08:54:24 -05:00
Zanie Blue	7e817bafde	Bump version to 0.8.10 (#15257)	2025-08-13 20:06:08 +00:00
Zanie Blue	68c0bf8a2c	Bump version to 0.8.9 (#15229)	2025-08-11 21:07:59 -05:00
Zanie Blue	9a54754b0a	Bump version to 0.8.8 (#15184)	2025-08-08 19:03:07 -05:00
Zanie Blue	8a22572338	Bump version to 0.8.7 (#15173)	2025-08-08 14:42:23 -05:00
Charlie Marsh	329a6b446a	Bump version to v0.8.6 (#15137)	2025-08-07 16:17:14 +01:00
Zanie Blue	ce37286814	Bump version to 0.8.5 (#15093)	2025-08-05 20:21:00 +00:00
Aaron Ang	3df972f18a	Support installing additional executables in uv tool install (#14014) ... Close #6314 ## Summary Continuing from #7592. Created a new PR to rebase the old branch with `main`, cleaned up test errors, and improved readability. ## Test Plan Same test cases as in #7592. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-07-30 14:50:24 -05:00
Zanie Blue	e176e17144	Bump version to 0.8.4 (#14980)	2025-07-30 16:24:20 +00:00
Zanie Blue	7e78f54e7c	Bump version to 0.8.3 (#14875)	2025-07-24 15:51:15 -05:00
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