## Summary

This adds Pyodide interpreter support in windows environment. In Pyodide
0.29.2, we made some enhancements to run Pyodide CLI in windows. This PR
relaxes a check that was disabling `uv pip` in Windows + Pyodide and
adds integration test.

## Test Plan

Added integration test, also tested locally by running

```
uv python install cpython-3.13.2-emscripten-wasm32-musl
uv venv venv-pyodide -p cpython-3.13.2-emscripten-wasm32-musl
call venv-pyodide\Scripts\activate
uv pip install packaging
python -c "import packaging"
```

…17456)

The `with_real_home()` method sets `HOME` to the real home directory,
which is required for tests that use the macOS keychain for
authentication. However, this causes a problem: when `HOME` is set but
`XDG_CONFIG_HOME` is not, uv resolves the config directory to
`$HOME/.config/uv` per the XDG specification. This means tests would
read the user's real configuration files (like `.python-version` or
`uv.toml`), which can override test-specified settings and cause
failures.

This PR sets `XDG_CONFIG_HOME` to the test's isolated config directory
in `with_real_home()`, ensuring that even when the real HOME is needed
for keychain access, configuration files are read from an isolated
location.

## Test plan

- Existing tests pass
- Tests using `with_real_home()` no longer read user config files

…tension` (#17710)

Co-authored-by: Claude <noreply@anthropic.com>

<!--
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 `fs-err` dependency to 3.2.2, because `uv` uses
`File::set_modified` in


https://github.com/astral-sh/uv/blob/2183c3fe1b4b8e83ea284f7b8ffbdc736f40332e/crates/uv-install-wheel/src/linker.rs#L337

and this API was added [in
3.2.2](https://github.com/andrewhickman/fs-err/blob/3.2.2/CHANGELOG.md#322).
<!-- What's the purpose of the change? What does it do, and why? -->

Version 3.2.2 was already in `Cargo.lock`, but I ran `cargo update
fs-error` and it made two small changes anyway.

## Test Plan

<!-- How was it tested? -->
There’s not much to test, as this just increases the minimum version.
You can verify the original problem by checking out `main` and running

```
$ cargo update fs-err --precise 3.2.1
$ cargo build
```

to see the error

```
error[E0599]: no method named `set_modified` found for struct `fs_err::File` in the current scope
   --> crates/uv-install-wheel/src/linker.rs:337:35
    |
337 |             if let Err(err) = dir.set_modified(now) {
    |                                   ^^^^^^^^^^^^ method not found in `fs_err::File`
```

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| debian | container | major | `bookworm` → `trixie` |

---

### 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:eyJjcmVhdGVkSW5WZXIiOiI0Mi45Mi4xIiwidXBkYXRlZEluVmVyIjoiNDIuOTIuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiYnVpbGQ6c2tpcC1yZWxlYXNlIiwiaW50ZXJuYWwiXX0=-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Zanie Blue <contact@zanie.dev>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

## Summary

If the file was already uploaded, `/validate` already tells us that.

Pick up python-build-standalone 20260127 for OpenSSL 3.5.5.

Co-authored-by: geofft <74644+geofft@users.noreply.github.com>

Closes #17722

Prepare for #17011

Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>

This matches the approach used by the trampoline in `bounce.rs` so we
combine the implementations in a new `uv-windows` crate.

Closes #17492
Closes #11817

This is loosely a copy of the `publish-docs` workflow. It uses
https://github.com/astral-sh/versions/blob/main/scripts/publish-version.py
to add the latest version in the cargo dist plan to that repository.