.tool-versions(uv) uv 0.12.1 -> 0.12.3

why: 0.12.3 is the newest uv past the 3-day window this setup applies to
package resolution (`exclude-newer` in the uv config, `min-release-age`
in .npmrc). Toolchain pins are resolved by mise and are not gated by
those settings, but holding the resolver binary itself to the same
window keeps one policy rather than two. 0.12.4 (2026-08-13) and 0.12.5
(2026-08-14) are both inside the window and are deliberately skipped.

what the release changes here: 0.12.2 adds CPython 3.14.7 and 0.12.3
adds 3.13.15, so the bare `3.14` and `3.13` entries in this file now
resolve to those patch releases. The rest of the span is performance
work that lands on every resolve: uv.lock parsing got faster for wheel
and source-distribution entries, Linux startup initializes the
workspace cache before spawning a thread, interpreter discovery no
longer reads procfs, and conflict-heavy resolutions avoid materializing
range complements. 0.12.2 also stops artifact sizes recorded in cached
wheels from breaking older uv versions reading the same cache.

- uv
  - https://github.com/astral-sh/uv/blob/0.12.2/CHANGELOG.md
  - https://github.com/astral-sh/uv/releases/tag/0.12.2
  - https://github.com/astral-sh/uv/blob/0.12.3/CHANGELOG.md
  - https://github.com/astral-sh/uv/releases/tag/0.12.3

Author: tony

.tool-versions

@@ -1,3 +1,3 @@
 just 1.58.0
-uv 0.12.1
+uv 0.12.3
 python 3.14 3.13 3.12 3.11 3.10