|
3 | 3 | <!-- prettier-ignore-start --> |
4 | 4 |
|
5 | 5 |
|
| 6 | +## 0.9.2 |
| 7 | + |
| 8 | +Released on 2025-10-10. |
| 9 | + |
| 10 | +### Python |
| 11 | + |
| 12 | +- Add CPython 3.9.24. |
| 13 | +- Add CPython 3.10.19. |
| 14 | +- Add CPython 3.11.14. |
| 15 | +- Add CPython 3.12.12. |
| 16 | + |
| 17 | +### Enhancements |
| 18 | + |
| 19 | +- Avoid inferring check URLs for pyx in `uv publish` ([#16234](https://github.com/astral-sh/uv/pull/16234)) |
| 20 | +- Add `uv tool list --show-python` ([#15814](https://github.com/astral-sh/uv/pull/15814)) |
| 21 | + |
| 22 | +### Documentation |
| 23 | + |
| 24 | +- Add missing "added in" to new environment variables in reference ([#16217](https://github.com/astral-sh/uv/pull/16217)) |
| 25 | + |
6 | 26 | ## 0.9.1 |
7 | 27 |
|
8 | 28 | Released on 2025-10-09. |
@@ -44,25 +64,25 @@ There are no breaking changes to [`uv_build`](https://docs.astral.sh/uv/concepts |
44 | 64 | ### Breaking changes |
45 | 65 |
|
46 | 66 | - **Python 3.14 is now the default stable version** |
47 | | - |
| 67 | + |
48 | 68 | The default Python version has changed from 3.13 to 3.14. This applies to Python version installation when no Python version is requested, e.g., `uv python install`. By default, uv will use the system Python version if present, so this may not cause changes to general use of uv. For example, if Python 3.13 is installed already, then `uv venv` will use that version. If no Python versions are installed on a machine and automatic downloads are enabled, uv will now use 3.14 instead of 3.13, e.g., for `uv venv` or `uvx python`. This change will not affect users who are using a `.python-version` file to pin to a specific Python version. |
49 | 69 | - **Allow use of free-threaded variants in Python 3.14+ without explicit opt-in** ([#16142](https://github.com/astral-sh/uv/pull/16142)) |
50 | | - |
| 70 | + |
51 | 71 | Previously, free-threaded variants of Python were considered experimental and required explicit opt-in (i.e., with `3.14t`) for usage. Now uv will allow use of free-threaded Python 3.14+ interpreters without explicit selection. The GIL-enabled build of Python will still be preferred, e.g., when performing an installation with `uv python install 3.14`. However, e.g., if a free-threaded interpreter comes before a GIL-enabled build on the `PATH`, it will be used. This change does not apply to free-threaded Python 3.13 interpreters, which will continue to require opt-in. |
52 | 72 | - **Use Python 3.14 stable Docker images** ([#16150](https://github.com/astral-sh/uv/pull/16150)) |
53 | | - |
| 73 | + |
54 | 74 | Previously, the Python 3.14 images had an `-rc` suffix, e.g., `python:3.14-rc-alpine` or |
55 | 75 | `python:3.14-rc-trixie`. Now, the `-rc` suffix has been removed to match the stable |
56 | 76 | [upstream images](https://hub.docker.com/_/python). The `-rc` images tags will no longer be |
57 | 77 | updated. This change should not break existing workflows. |
58 | 78 | - **Upgrade Alpine Docker image to Alpine 3.22** |
59 | | - |
| 79 | + |
60 | 80 | Previously, the `uv:alpine` Docker image was based on Alpine 3.21. Now, this image is based on Alpine 3.22. The previous image can be recovered with `uv:alpine3.21` and will continue to be updated until a future release. |
61 | 81 | - **Upgrade Debian Docker images to Debian 13 "Trixie"** |
62 | | - |
| 82 | + |
63 | 83 | Previously, the `uv:debian` and `uv:debian-slim` Docker images were based on Debian 12 "Bookworm". Now, these images are based on Debian 13 "Trixie". The previous images can be recovered with `uv:bookworm` and `uv:bookworm-slim` and will continue to be updated until a future release. |
64 | 84 | - **Fix incorrect output path when a trailing `/` is used in `uv build`** ([#15133](https://github.com/astral-sh/uv/pull/15133)) |
65 | | - |
| 85 | + |
66 | 86 | When using `uv build` in a workspace, the artifacts are intended to be written to a `dist` directory in the workspace root. A bug caused workspace root determination to fail when the input path included a trailing `/` causing the `dist` directory to be placed in the child directory. This bug has been fixed in this release. For example, `uv build child/` is used, the output path will now be in `<workspace root>/dist/` rather than `<workspace root>/child/dist/`. |
67 | 87 |
|
68 | 88 | ### Python |
|
0 commit comments