a47ae0cd35
Update docker/login-action action to v4 ( #18500 )
...
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [docker/login-action](https://redirect.github.com/docker/login-action )
| action | major | `v3.7.0` → `v4.0.0` |
---
### Release Notes
<details>
<summary>docker/login-action (docker/login-action)</summary>
###
[`v4.0.0`](https://redirect.github.com/docker/login-action/releases/tag/v4.0.0 )
[Compare
Source](https://redirect.github.com/docker/login-action/compare/v3.7.0...v4.0.0 )
- Node 24 as default runtime (requires [Actions Runner
v2.327.1](https://redirect.github.com/actions/runner/releases/tag/v2.327.1 )
or later) by [@​crazy-max](https://redirect.github.com/crazy-max )
in
[#​929](https://redirect.github.com/docker/login-action/pull/929 )
- Switch to ESM and update config/test wiring by
[@​crazy-max](https://redirect.github.com/crazy-max ) in
[#​927](https://redirect.github.com/docker/login-action/pull/927 )
- Bump [@​actions/core](https://redirect.github.com/actions/core )
from 1.11.1 to 3.0.0 in
[#​919](https://redirect.github.com/docker/login-action/pull/919 )
- Bump
[@​aws-sdk/client-ecr](https://redirect.github.com/aws-sdk/client-ecr )
from 3.890.0 to 3.1000.0 in
[#​909](https://redirect.github.com/docker/login-action/pull/909 )
[#​920](https://redirect.github.com/docker/login-action/pull/920 )
- Bump
[@​aws-sdk/client-ecr-public](https://redirect.github.com/aws-sdk/client-ecr-public )
from 3.890.0 to 3.1000.0 in
[#​909](https://redirect.github.com/docker/login-action/pull/909 )
[#​920](https://redirect.github.com/docker/login-action/pull/920 )
- Bump
[@​docker/actions-toolkit](https://redirect.github.com/docker/actions-toolkit )
from 0.63.0 to 0.77.0 in
[#​910](https://redirect.github.com/docker/login-action/pull/910 )
[#​928](https://redirect.github.com/docker/login-action/pull/928 )
- Bump
[@​isaacs/brace-expansion](https://redirect.github.com/isaacs/brace-expansion )
from 5.0.0 to 5.0.1 in
[#​921](https://redirect.github.com/docker/login-action/pull/921 )
- Bump js-yaml from 4.1.0 to 4.1.1 in
[#​901](https://redirect.github.com/docker/login-action/pull/901 )
**Full Changelog**:
<https://github.com/docker/login-action/compare/v3.7.0...v4.0.0 >
</details>
---
### Configuration
📅 **Schedule**: Branch creation - Between 12:00 AM and 03:59 AM, only on
Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule
defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/ ).
View the [repository job
log](https://developer.mend.io/github/astral-sh/uv ).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My42Ni40IiwidXBkYXRlZEluVmVyIjoiNDMuNjYuNCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiYnVpbGQ6c2tpcC1kb2NrZXIiLCJidWlsZDpza2lwLXJlbGVhc2UiLCJpbnRlcm5hbCJdfQ==-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2026-03-18 08:15:40 -05:00
8998568ef4
Detect hard-float support on aarch64 kernels running armv7 userspace ( #18530 )
...
Pulled out of https://github.com/astral-sh/uv/pull/18517
I don't have aarch64 hardware available locally, but Claude posited:
> When an armv7 binary runs on an aarch64 kernel (e.g., armv7l
containers on aarch64 hosts, or 32-bit Raspberry Pi OS on 64-bit
hardware), /proc/cpuinfo reports aarch64-style feature flags instead of
armv7 flags. The existing check for "vfp" fails because aarch64 uses
"fp" instead.
>
> Add detection of the aarch64 "fp" feature flag (mandatory on all
aarch64 CPUs) as a discrete token, indicating hardware floating-point
support. This ensures uv selects the gnueabihf (hard-float) Python
variant instead of the gnueabi (soft-float) variant.
I reproduced this in https://github.com/astral-sh/uv/pull/18532
Under QEMU on aarch64 macOS, both the `vfp` and `fp` feature flags are
set.
Closes #18509
2026-03-18 07:52:31 -05:00
87950df2cc
Add pypy 3.11.15 ( #18468 )
...
Automated update for Python releases.
Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com >
2026-03-18 07:48:18 -05:00
287faaf92c
Move Rust and Python version support out of the Platform support policy ( #18535 )
...
The content is unchanged.
I'm planning to expand the content in the Python version and Platform
support files and generally don't like that these are mixed.
2026-03-18 07:47:21 -05:00
7b3170d69d
Treat abi3 wheel Python version as a lower bound ( #18536 )
...
## Summary
`flashinfer_jit_cache-0.5.3+cu130-cp39-abi3-manylinux_2_28_x86_64.whl`
needs to be interpreted as "Python 3.9 or later", but our "implied
markers" coverage was interpreting it as `==3.9.*`.
Closes https://github.com/astral-sh/uv/issues/18527 .
2026-03-17 23:33:26 +00:00
17afca33e9
Upgrade the release build runners from Windows 2022 -> 2025 ( #18528 )
...
Needed for WinGet in #17543
The `windows-latest` label already changed
https://github.blog/changelog/2025-07-31-github-actions-new-apis-and-windows-latest-migration-notice/
I don't think this should affect users.
2026-03-17 15:13:20 -05:00
457aded048
Bump astral-tokio-tar to 0.6.0 ( #18507 )
...
## Summary
See GHSA-6gx3-4362-rf54.
## Test Plan
NFC.
Signed-off-by: William Woodruff <william@astral.sh >
2026-03-17 01:28:34 +00:00
006b56b12d
Bump version to 0.10.11 ( #18521 )
...
Co-authored-by: Tomasz Kramkowski <tom@astral.sh >
2026-03-16 19:32:39 -04:00
4d4b968f25
Deprecate some non-PEP 625 source distributions ( #17467 )
2026-03-17 08:18:09 +09:00
de2071881e
Run benchmarks in offline mode ( #18487 )
...
Currently, we have the simulated benchmarks on codspeed turned of, they
flake to much
(https://codspeed.io/astral-sh/uv/benchmarks/crates/uv-bench/benches/uv.rs::uv::resolve_warm_airflow::resolve_warm_airflow?runnerMode=Simulation&period=1m ),
while the walltime benchmarks are kinda stable.
<img width="1819" height="996" alt="image"
src="https://github.com/user-attachments/assets/ffd7b5b5-3bf9-427b-92dc-0bb4fbfbb3d0 "
/>
<img width="1819" height="955" alt="image"
src="https://github.com/user-attachments/assets/8d1a7519-4214-4564-b7a5-c899bff4f7b4 "
/>
Looking into two of these spurious regressions, we see that they occur
in the network code, and that the CI runs for them took >10min, while
regularly runs take <10min.
*
https://codspeed.io/astral-sh/uv/runs/compare/699738846a7b43e19b4d2e67..699778f1f92bec70ac9b3024?uri=crates%2Fuv-bench%2Fbenches%2Fuv.rs%3A%3Auv%3A%3Aresolve_warm_airflow%3A%3Aresolve_warm_airflow&runnerMode=Simulation
*
https://github.com/astral-sh/uv/actions/runs/22199337000/job/64207958534
*
https://codspeed.io/astral-sh/uv/runs/compare/699caa16bfa44e7f9c0b44c5..699cc8e475e640df09b7f01f?uri=crates%2Fuv-bench%2Fbenches%2Fuv.rs%3A%3Auv%3A%3Aresolve_warm_airflow%3A%3Aresolve_warm_airflow&runnerMode=Simulation
*
https://github.com/astral-sh/uv/actions/runs/22325481213/job/64594783994
<img width="1819" height="973" alt="image"
src="https://github.com/user-attachments/assets/e5c7c260-3a93-4e25-bc00-fdf045edc098 "
/>
uv caches PyPI responses for 10min, after that, it has to make
revalidation request. If the build takes >7min, and we prime the caches
before the build, the most likely explanation is that these runs have to
make revalidation requests. This is not a problem for walltime
benchmarks, which run multiple times, where revalidation requests in one
run are just an outlier that gets ignored overall.
The fix is that the benchmark itself primes the cache, and then runs in
offline mode. We keep the cache priming in the GitHub action before the
benchmark builds for the sake of the job logs, while we need the priming
inside the bench for running `cargo bench` locally without extra setup.
Running the benches themselves with an offline client make uv ignore the
10min threshold.
2026-03-16 15:14:54 -05:00
add312b679
Allow --project to refer to a pyproject.toml directly and reduce to a warning on other files ( #18513 )
...
Closes https://github.com/astral-sh/uv/issues/18508
This unintentionally regressed in
https://github.com/astral-sh/uv/pull/17714 as it appeared that
`--project <file>` always failed but it actually succeeds if the file is
has an ancestor directory with a `pyproject.toml`.
This also removes the warning for `--project [path/]pyproject.toml` as I
think that's a fine use-case.
---------
Co-authored-by: Claude <noreply@anthropic.com >
2026-03-16 15:14:31 -05:00
ebdd2bf4b9
Update zizmorcore/zizmor-action action to v0.5.2 ( #18496 )
2026-03-16 14:44:10 -04:00
6bde8a4e63
Update taiki-e/install-action action to v2.68.25 ( #18495 )
2026-03-16 14:43:54 -04:00
8f9dff80a5
Update Rust crate jiff to v0.2.23 ( #18491 )
...
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [jiff](https://redirect.github.com/BurntSushi/jiff ) |
workspace.dependencies | patch | `0.2.22` → `0.2.23` |
---
### Release Notes
<details>
<summary>BurntSushi/jiff (jiff)</summary>
###
[`v0.2.23`](https://redirect.github.com/BurntSushi/jiff/blob/HEAD/CHANGELOG.md#0223-2026-03-03 )
[Compare
Source](https://redirect.github.com/BurntSushi/jiff/compare/0.2.22...0.2.23 )
\===================
This release updates Jiff's bundled copy of the \[IANA Time Zone
Database]
to `2026a`. See the [`2026a` release announcement] for more details.
[`2026a` release announcement]:
https://lists.iana.org/hyperkitty/list/tz-announce@iana.org/thread/ASPLBE3A4BAEXIOQ3KZ6EJSJWBU6L53G/
</details>
---
### Configuration
📅 **Schedule**: Branch creation - Between 12:00 AM and 03:59 AM, only on
Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule
defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/ ).
View the [repository job
log](https://developer.mend.io/github/astral-sh/uv ).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My42Ni40IiwidXBkYXRlZEluVmVyIjoiNDMuNjYuNCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiYnVpbGQ6c2tpcC1kb2NrZXIiLCJidWlsZDpza2lwLXJlbGVhc2UiLCJpbnRlcm5hbCJdfQ==-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2026-03-16 18:43:43 +00:00
7514a0e0d7
Update Rust crate cargo-util to v0.2.27 ( #18490 )
2026-03-16 14:42:42 -04:00
d52c38980f
Update dependency astral-sh/uv to v0.10.10 ( #18489 )
2026-03-16 14:41:43 -04:00
59123af42a
Update CodSpeedHQ/action action to v4.11.1 ( #18488 )
2026-03-16 14:41:37 -04:00
2204837912
Update Rust crate quote to v1.0.45 ( #18492 )
2026-03-16 14:39:28 -04:00
58f1387b44
Update Rust crate rustix to v1.1.4 ( #18493 )
2026-03-16 14:36:47 -04:00
fc9b8fdb39
Update Rust crate which to v8.0.2 ( #18494 )
2026-03-16 14:36:10 -04:00
df1c310d7c
Update Rust crate tokio to v1.50.0 ( #18498 )
2026-03-16 14:35:53 -04:00
321c374479
Update Rust crate uuid to v1.22.0 ( #18499 )
2026-03-16 14:35:45 -04:00
a2ae16190e
Upgrade transitive Rust dependencies ( #18483 )
...
These are not managed by Renovate.
I wrote a script to do this, which I may commit separately. I used an
LLM to review each changelog for relevant changes as well as each diff
for malicious content.
2026-03-16 13:29:13 -05:00
24d81d2bf4
Update astral-sh/setup-uv action to v7.6.0 ( #18515 )
...
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2026-03-16 17:19:45 +00:00
7b6a5159f1
Make resolver dependency edges source-aware across forks ( #18435 )
...
## Summary
This is a non-behavior-changing refactor that puts direct source
information on individual `PubGrubDependency` edges. The resulting code
is, in my opinion, a bit simpler with clearer abstractions and more
consistent handling.
2026-03-16 08:19:00 -04:00
99de5322c5
Enforce available distributions for supported environments ( #18451 )
...
## Summary
A revival of https://github.com/astral-sh/uv/pull/17118 . We now enforce
that builds are available for all supported environments in addition to
required environments.
Closes https://github.com/astral-sh/uv/issues/17067 .
Closes https://github.com/astral-sh/uv/issues/17060 .
2026-03-16 07:56:21 -04:00
5606d963fc
Fetch Ruff release metadata from an Astral mirror ( #18358 )
2026-03-16 10:50:39 +00:00
f8bd28ac4b
Use PEP 639 license metadata for uv itself ( #16477 )
...
<!--
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
In [pep 639](https://peps.python.org/pep-0639/ ) the classifier for
licenses gets deprecated in favor of the license field.
The benefits for UV:
- Clear that you can pick a license, not have to have both
- Clear it is version 2 for the Apache license
https://peps.python.org/pep-0639/
## Test Plan
Builds, works.
If the license shows up in pypi.org with the SPDX operator, it works
2026-03-15 21:34:35 +00:00
efdf905f82
Add missing -o requirements.txt in uv pip compile example ( #12308 )
...
## Summary
`uv pip compile` doesn't produce `requirements.txt` without `-o
requirements.txt` option.
2026-03-15 21:34:14 +00:00
5f77df89fb
Improve distribution id performance ( #18486 )
...
Improve the performance for https://github.com/astral-sh/uv/pull/18373 .
```
$ hyperfine --warmup 3 --runs 30 \
'/tmp/uv-0-baseline lock --project /home/konsti/projects/airflow' \
'/tmp/uv-1-or-insert-with lock --project /home/konsti/projects/airflow' \
'/tmp/uv-2-single-lookup lock --project /home/konsti/projects/airflow' \
Benchmark 1: /tmp/uv-0-baseline lock --project /home/konsti/projects/airflow
Time (mean ± σ): 147.1 ms ± 10.1 ms [User: 108.4 ms, System: 23.6 ms]
Range (min … max): 130.5 ms … 165.9 ms 30 runs
Benchmark 2: /tmp/uv-1-or-insert-with lock --project /home/konsti/projects/airflow
Time (mean ± σ): 141.3 ms ± 7.3 ms [User: 106.3 ms, System: 21.3 ms]
Range (min … max): 131.5 ms … 160.6 ms 30 runs
Benchmark 3: /tmp/uv-2-single-lookup lock --project /home/konsti/projects/airflow
Time (mean ± σ): 139.6 ms ± 7.3 ms [User: 104.7 ms, System: 21.8 ms]
Range (min … max): 128.3 ms … 160.9 ms 30 runs
Summary
/tmp/uv-2-single-lookup lock --project /home/konsti/projects/airflow ran
1.01 ± 0.07 times faster than /tmp/uv-1-or-insert-with lock --project /home/konsti/projects/airflow
1.05 ± 0.09 times faster than /tmp/uv-0-baseline lock --project /home/konsti/projects/airflow
```
2026-03-15 20:29:04 +01:00
ea786e5b17
Link to the AI policy in the contributing guide ( #18448 )
2026-03-15 07:43:01 -05:00
34f967310f
Add an integration test for Intel conda ( #18461 )
...
Reproduces #14267 — see
https://github.com/astral-sh/uv/actions/runs/23076175099/job/67037153580
Which is resolved by https://github.com/astral-sh/uv/pull/18452 — see
https://github.com/astral-sh/uv/actions/runs/23090030294/job/67074278041
2026-03-14 17:57:49 +00:00
fe5ca6ca80
Disable SYSTEM_VERSION_COMPAT when querying interpreters on macOS ( #18452 )
...
Closes https://github.com/astral-sh/uv/issues/14267
Replaces https://github.com/astral-sh/uv/pull/18436 — adding my review
because I cannot push there
Replaces https://github.com/astral-sh/uv/pull/18416
---------
Co-authored-by: Ed Schofield <ed@pythoncharmers.com >
2026-03-14 12:45:37 -05:00
0507193eb6
Pin termux test packages to improve job stability ( #18480 )
...
I'm seeing this flake when the package index is partially changed. I'm
_hoping_ this resolve that issue?
See
https://github.com/astral-sh/uv/actions/runs/23090030294/job/67073331237?pr=18461
for example
---------
Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com >
2026-03-14 10:22:36 -05:00
a5d82ab430
Link to organization security policy ( #18449 )
2026-03-14 10:13:54 -05:00
08abfdbb81
Use settings::resolve_preview for project validation ( #18447 )
...
## Summary
The affected code was manually implementing part of the full logic which
was already available in `settings::resolve_preview` so this PR just
makes the project validation code use this function instead.
## Test Plan
Existing test coverage.
2026-03-14 14:20:45 +00:00
45ea4dd4ec
Fix uv sync --active recreating active environments when UV_PYTHON_INSTALL_DIR is relative ( #18398 )
...
## Summary
We need to normalize any relative managed-Python install roots before
checking whether the active environment’s interpreter is uv-managed, so
that `sync --active` reuses the environment.
Closes https://github.com/astral-sh/uv/issues/16631 .
2026-03-13 18:47:53 -05:00
1375fdb70d
Upgrade rmp -> 0.8.15 dropping paste ( #18466 )
...
Resolves
https://scout.docker.com/vulnerabilities/id/RUSTSEC-2024-0436?s=rustsec&n=paste&t=cargo&vr=%3E%3D0.0.0-0
2026-03-13 18:12:06 -05:00
d04f25d1b7
Create release branch and commit automatically ( #18456 )
2026-03-13 18:10:24 -05:00
9753c0991b
Run the integration tests on changes ( #18465 )
2026-03-13 17:45:24 -05:00
9dba9c7007
Update Rust crate nix to 0.31.2 ( #17934 )
2026-03-13 21:04:00 +00:00
d64ffcb37e
Update uds_windows to v1.2.0 ( #18463 )
2026-03-13 20:52:04 +00:00
8337ffaffd
Update Rust crate wmi to 0.18.3 ( #17602 )
...
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [wmi](https://redirect.github.com/ohadravid/wmi-rs ) |
workspace.dependencies | minor | `0.16.0` → `0.18.0` |
---
### Release Notes
<details>
<summary>ohadravid/wmi-rs (wmi)</summary>
###
[`v0.18.0`](https://redirect.github.com/ohadravid/wmi-rs/releases/tag/v0.18.0 )
[Compare
Source](https://redirect.github.com/ohadravid/wmi-rs/compare/v0.17.3...v0.18.0 )
#### What's Changed
- Remove `COMLibrary` and let `WMIConnection` initialize COM if needed
by [@​ohadravid](https://redirect.github.com/ohadravid ) in
[#​137](https://redirect.github.com/ohadravid/wmi-rs/pull/137 )
You can now call `WMIConnection::new()` and let the crate handle the
initialization internally.
Note: COM will NOT be uninitialized when the connection is dropped
(similar to <=0.17 versions, which didn't uninitialize COM on drop since
[#​53](https://redirect.github.com/ohadravid/wmi-rs/issues/53 )).
If this is not what you want, then you must initialize COM yourself
**before** creating the connection. See the docs for more.
- Update the crate to Rust 2024 edition
**Full Changelog**:
<https://github.com/ohadravid/wmi-rs/compare/v0.17.3...v0.18.0 >
###
[`v0.17.3`](https://redirect.github.com/ohadravid/wmi-rs/releases/tag/v0.17.3 )
[Compare
Source](https://redirect.github.com/ohadravid/wmi-rs/compare/v0.17.2...v0.17.3 )
#### What's Changed
- chore(deps): update criterion requirement from 0.5 to 0.6 by
[@​dependabot](https://redirect.github.com/dependabot )\[bot] in
[#​128](https://redirect.github.com/ohadravid/wmi-rs/pull/128 )
- Update CI images by
[@​ohadravid](https://redirect.github.com/ohadravid ) in
[#​135](https://redirect.github.com/ohadravid/wmi-rs/pull/135 )
- chore(deps): update windows requirement from 0.61 to 0.62 by
[@​dependabot](https://redirect.github.com/dependabot )\[bot] in
[#​134](https://redirect.github.com/ohadravid/wmi-rs/pull/134 )
**Full Changelog**:
<https://github.com/ohadravid/wmi-rs/compare/v0.17.2...v0.17.3 >
###
[`v0.17.2`](https://redirect.github.com/ohadravid/wmi-rs/releases/tag/v0.17.2 )
[Compare
Source](https://redirect.github.com/ohadravid/wmi-rs/compare/v0.17.1...v0.17.2 )
#### What's Changed
- feat(remote\_connection): added with\_credentials() by
[@​hatch15](https://redirect.github.com/hatch15 ) in
[#​127](https://redirect.github.com/ohadravid/wmi-rs/pull/127 )
#### New Contributors
- [@​hatch15](https://redirect.github.com/hatch15 ) made their
first contribution in
[#​127](https://redirect.github.com/ohadravid/wmi-rs/pull/127 )
**Full Changelog**:
<https://github.com/ohadravid/wmi-rs/compare/v0.17.1...v0.17.2 >
###
[`v0.17.1`](https://redirect.github.com/ohadravid/wmi-rs/releases/tag/v0.17.1 )
[Compare
Source](https://redirect.github.com/ohadravid/wmi-rs/compare/v0.17.0...v0.17.1 )
#### What's Changed
- Support arrays of IUnknown pointers by
[@​samin-cf](https://redirect.github.com/samin-cf ) in
[#​125](https://redirect.github.com/ohadravid/wmi-rs/pull/125 ) and
[@​ohadravid](https://redirect.github.com/ohadravid ) in
[#​126](https://redirect.github.com/ohadravid/wmi-rs/pull/126 )
**Full Changelog**:
<https://github.com/ohadravid/wmi-rs/compare/v0.17.0...v0.17.1 >
###
[`v0.17.0`](https://redirect.github.com/ohadravid/wmi-rs/releases/tag/v0.17.0 )
[Compare
Source](https://redirect.github.com/ohadravid/wmi-rs/compare/v0.16.0...v0.17.0 )
#### What's Changed
- Added support for Option by
[@​vpopescu](https://redirect.github.com/vpopescu ) in
[#​122](https://redirect.github.com/ohadravid/wmi-rs/pull/122 )
#### Breaking Changes
- Fixed conversions from Rust types to WMI types (so, only when used for
method calling or using put\_property), which were incorrect in a few
cases (notably, u32s and u16s were not converted correctly), and added
some missing conversions, in
[#​124](https://redirect.github.com/ohadravid/wmi-rs/pull/124 )
- `SafeArrayAccessor::new` now accepts a `NonNull<SAFEARRAY>` instead of
a reference, in
[#​124](https://redirect.github.com/ohadravid/wmi-rs/pull/124 )
#### New Contributors
- [@​vpopescu](https://redirect.github.com/vpopescu ) made their
first contribution in
[#​122](https://redirect.github.com/ohadravid/wmi-rs/pull/122 )
**Full Changelog**:
<https://github.com/ohadravid/wmi-rs/compare/v0.16.0...v0.17.0 >
</details>
---
### Configuration
📅 **Schedule**: Branch creation - Between 12:00 AM and 03:59 AM, only on
Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule
defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/ ).
View the [repository job
log](https://developer.mend.io/github/astral-sh/uv ).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi43NC41IiwidXBkYXRlZEluVmVyIjoiNDIuNzQuNSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiaW50ZXJuYWwiXX0=-->
---------
Co-authored-by: konstin <konstin@mailbox.org >
Co-authored-by: Zanie Blue <contact@zanie.dev >
2026-03-13 20:32:00 +00:00
cb109d4808
Update codspeed crates to v4.4.1 ( #18462 )
...
The latest version fixed the repository URL.
2026-03-13 20:23:51 +00:00
91b73925e2
Run macOS tests whenever we build release binaries ( #18458 )
2026-03-13 19:47:01 +00:00
8c730aaad6
Bump version to 0.10.10 ( #18455 )
2026-03-13 14:35:08 -05:00
f190514288
Improve error handling for platform detection in Python downloads ( #18453 )
...
I noticed this weird error chain in
https://github.com/astral-sh/uv/issues/8635#issuecomment-4055185865
```
error: Failed to parse request part
Caused by: Could not read ELF interpreter from any of the following paths: /bin/sh, /usr/bin/env, /bin/dash, /bin/ls
```
Co-authored-by: Claude <noreply@anthropic.com >
2026-03-13 19:11:05 +00:00
3f03c64a0a
Update Rust to v1.94.0 ( #18442 )
...
This PR contains the following updates:
| Package | Update | Change |
|---|---|---|
| [rust](https://redirect.github.com/rust-lang/rust ) | minor | `1.93` →
`1.94.0` |
---
### Release Notes
<details>
<summary>rust-lang/rust (rust)</summary>
###
[`v1.94.0`](https://redirect.github.com/rust-lang/rust/blob/HEAD/RELEASES.md#Version-1940-2026-03-05 )
[Compare
Source](https://redirect.github.com/rust-lang/rust/compare/1.93.1...1.94.0 )
\==========================
<a id="1.94.0-Language"></a>
## Language
- [Impls and impl items inherit `dead_code` lint level of the
corresponding traits and trait
items](https://redirect.github.com/rust-lang/rust/pull/144113 )
- [Stabilize additional 29 RISC-V target features including large
portions of the RVA22U64 / RVA23U64
profiles](https://redirect.github.com/rust-lang/rust/pull/145948 )
- [Add warn-by-default `unused_visibilities` lint for visibility on
`const _`
declarations](https://redirect.github.com/rust-lang/rust/pull/147136 )
- [Update to Unicode
17](https://redirect.github.com/rust-lang/rust/pull/148321 )
- [Avoid incorrect lifetime errors for
closures](https://redirect.github.com/rust-lang/rust/pull/148329 )
<a id="1.94.0-Platform-Support"></a>
## Platform Support
- [Add `riscv64im-unknown-none-elf` as a tier 3
target](https://redirect.github.com/rust-lang/rust/pull/148790 )
Refer to Rust's [platform support page][platform-support-doc]
for more information on Rust's tiered platform support.
[platform-support-doc]:
https://doc.rust-lang.org/rustc/platform-support.html
<a id="1.94.0-Libraries"></a>
## Libraries
- [Relax `T: Ord` bound for some `BinaryHeap<T>`
methods.](https://redirect.github.com/rust-lang/rust/pull/149408 )
<a id="1.94.0-Stabilized-APIs"></a>
## Stabilized APIs
-
[`<[T]>::array_windows`](https://doc.rust-lang.org/stable/std/primitive.slice.html#method.array_windows )
-
[`<[T]>::element_offset`](https://doc.rust-lang.org/stable/std/primitive.slice.html#method.element_offset )
-
[`LazyCell::get`](https://doc.rust-lang.org/stable/std/cell/struct.LazyCell.html#method.get )
-
[`LazyCell::get_mut`](https://doc.rust-lang.org/stable/std/cell/struct.LazyCell.html#method.get_mut )
-
[`LazyCell::force_mut`](https://doc.rust-lang.org/stable/std/cell/struct.LazyCell.html#method.force_mut )
-
[`LazyLock::get`](https://doc.rust-lang.org/stable/std/sync/struct.LazyLock.html#method.get )
-
[`LazyLock::get_mut`](https://doc.rust-lang.org/stable/std/sync/struct.LazyLock.html#method.get_mut )
-
[`LazyLock::force_mut`](https://doc.rust-lang.org/stable/std/sync/struct.LazyLock.html#method.force_mut )
- [`impl TryFrom<char> for
usize`](https://doc.rust-lang.org/stable/std/convert/trait.TryFrom.html#impl-TryFrom%3Cchar%3E-for-usize )
-
[`std::iter::Peekable::next_if_map`](https://doc.rust-lang.org/stable/std/iter/struct.Peekable.html#method.next_if_map )
-
[`std::iter::Peekable::next_if_map_mut`](https://doc.rust-lang.org/stable/std/iter/struct.Peekable.html#method.next_if_map_mut )
- [x86 `avx512fp16`
intrinsics](https://redirect.github.com/rust-lang/rust/issues/127213 )
(excluding those that depend directly on the unstable `f16` type)
- [AArch64 NEON fp16
intrinsics](https://redirect.github.com/rust-lang/rust/issues/136306 )
(excluding those that depend directly on the unstable `f16` type)
-
[`f32::consts::EULER_GAMMA`](https://doc.rust-lang.org/stable/std/f32/consts/constant.EULER_GAMMA.html )
-
[`f64::consts::EULER_GAMMA`](https://doc.rust-lang.org/stable/std/f64/consts/constant.EULER_GAMMA.html )
-
[`f32::consts::GOLDEN_RATIO`](https://doc.rust-lang.org/stable/std/f32/consts/constant.GOLDEN_RATIO.html )
-
[`f64::consts::GOLDEN_RATIO`](https://doc.rust-lang.org/stable/std/f64/consts/constant.GOLDEN_RATIO.html )
These previously stable APIs are now stable in const contexts:
-
[`f32::mul_add`](https://doc.rust-lang.org/stable/std/primitive.f32.html#method.mul_add )
-
[`f64::mul_add`](https://doc.rust-lang.org/stable/std/primitive.f64.html#method.mul_add )
<a id="1.94.0-Cargo"></a>
## Cargo
- Stabilize the config include key. The top-level include config key
allows loading additional config files, enabling better organization,
sharing, and management of Cargo configurations across projects and
environments.
[docs](https://doc.rust-lang.org/nightly/cargo/reference/config.html#including-extra-configuration-files )
[#​16284](https://redirect.github.com/rust-lang/cargo/pull/16284 )
- Stabilize the pubtime field in registry index. This records when a
crate version was published and enables time-based dependency resolution
in the future. Note that crates.io will gradually backfill existing
packages when a new version is published. Not all crates have pubtime
yet.
[#​16369](https://redirect.github.com/rust-lang/cargo/pull/16369 )
[#​16372](https://redirect.github.com/rust-lang/cargo/pull/16372 )
- Cargo now parses [TOML v1.1](https://toml.io/en/v1.1.0 ) for manifests
and configuration files. Note that using these features in Cargo.toml
will raise your development MSRV, but the published manifest remains
compatible with older parsers.
[#​16415](https://redirect.github.com/rust-lang/cargo/pull/16415 )
- [Make `CARGO_BIN_EXE_<crate>` available at runtime
](https://redirect.github.com/rust-lang/cargo/pull/16421/ )
<a id="1.94.0-Compatibility-Notes"></a>
## Compatibility Notes
- [Forbid freely casting lifetime bounds of
`dyn`-types](https://redirect.github.com/rust-lang/rust/pull/136776 )
- [Make closure capturing have consistent and correct behaviour around
patterns](https://redirect.github.com/rust-lang/rust/pull/138961 )
Some finer details of how precise closure captures get affected by
pattern matching have been changed. In some cases, this can cause a
non-move closure that was previously capturing an entire variable by
move, to now capture only part of that variable by move, and other parts
by borrow. This can cause the borrow checker to complain where it
previously didn't, or cause `Drop` to run at a different point in time.
- [Standard library macros are now imported via prelude, not via
injected
`#[macro_use]`](https://redirect.github.com/rust-lang/rust/pull/139493 )
This will raise an error if macros of the same name are glob imported.
For example if a crate defines their own `matches` macro and then glob
imports that,
it's now ambiguous whether the custom or standard library `matches` is
meant and
an explicit import of the name is required to resolve the ambiguity.
One exception is `core::panic` and `std::panic`, if their import is
ambiguous
a new warning
([`ambiguous_panic_imports`](https://redirect.github.com/rust-lang/rust/issues/147319 ))
is raised.
This may raise a new warning
([`ambiguous_panic_imports`](https://redirect.github.com/rust-lang/rust/issues/147319 ))
on `#![no_std]` code glob importing the std crate.
Both `core::panic!` and `std::panic!` are then in scope and which is
used is ambiguous.
- [Don't strip shebang in expression-context
`include!(…)`s](https://redirect.github.com/rust-lang/rust/pull/146377 )
This can cause previously working includes to no longer compile if they
included files which started with a shebang.
- [Ambiguous glob reexports are now also visible
cross-crate](https://redirect.github.com/rust-lang/rust/pull/147984 )
This unifies behavior between local and cross-crate errors on these
exports, which may introduce new ambiguity errors.
- [Don't normalize where-clauses before checking
well-formedness](https://redirect.github.com/rust-lang/rust/pull/148477 )
- [Introduce a future compatibility warning on codegen attributes on
body-free trait
methods](https://redirect.github.com/rust-lang/rust/pull/148756 )
These attributes currently have no effect in this position.
- [On Windows `std::time::SystemTime::checked_sub_duration` will return
`None` for times before the Windows epoch
(1/1/1601)](https://redirect.github.com/rust-lang/rust/pull/148825 )
- [Lifetime identifiers such as `'a` are now NFC
normalized](https://redirect.github.com/rust-lang/rust/pull/149192 ).
- [Overhaul filename handling for cross-compiler
consistency](https://redirect.github.com/rust-lang/rust/pull/149709 )
Any paths emitted by compiler now always respect the relative-ness of
the paths and `--remap-path-prefix` given originally.
One side-effect of this change is that paths emitted for local crates in
Cargo (path dependencies and workspace members) are no longer absolute
but relative when emitted as part of a diagnostic in a downstream crate.
<a id="1.94.0-Internal-Changes"></a>
## Internal Changes
These changes do not affect any public interfaces of Rust, but they
represent
significant improvements to the performance or internals of rustc and
related
tools.
- [Switch to `annotate-snippets` for error
emission](https://redirect.github.com/rust-lang/rust/pull/150032 )
This should preserve mostly the same outputs in rustc error messages.
</details>
---
### Configuration
📅 **Schedule**: Branch creation - Between 12:00 AM and 03:59 AM, only on
Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule
defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/ ).
View the [repository job
log](https://developer.mend.io/github/astral-sh/uv ).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My42Ni40IiwidXBkYXRlZEluVmVyIjoiNDMuNjYuNCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiYnVpbGQ6c2tpcC1kb2NrZXIiLCJidWlsZDpza2lwLXJlbGVhc2UiLCJpbnRlcm5hbCJdfQ==-->
---------
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Zanie Blue <contact@zanie.dev >
2026-03-13 13:59:55 -05:00
078feb7474
Remove the repository code of conduct in favor of the organization one ( #18450 )
...
This roughly appears to be working per
https://github.com/astral-sh/uv/tree/zb/coc-org?tab=coc-ov-file
2026-03-13 13:47:46 -05:00
3db30e048d
Filter out unsupported environment wheels ( #18445 )
...
## Summary
The issue here is that once conflicts are introduced, the markers in the
lockfile get too complicated for our basic environment checks. We should
_also_ filter by supported environments here.
Closes https://github.com/astral-sh/uv/issues/18428 .
2026-03-13 14:46:27 -04:00
renovate[bot]