64 signals · 74 observation events
An extremely fast Python package and project manager, written in Rust.
0.12.3Prereleases and milestones indicate public plans; they are not delivery commitments.
## Summary We have `from_registry_requirement` that does the equivalent of all of this code. (Cleanup in preparation for PR to fix #20477.) ## Test Plan Existing coverage.
Reverts astral-sh/uv#21055, CodSpeed team reports that their backend can now support uv's samply results
Projects with checked-in type stubs may not require building their native extensions for type checking, but `uv check` always installs the project while synchronizing its dependencies. Support `--no-install-project` and `UV_NO_INSTALL_PROJECT` so those projects can install their dependencies and run checks without building or installing themselves. Fixes ast
## Summary `uv check` runs `ty check` in a separate process, but previously applied terminal settings only to uv itself. As a result, ty could still emit colored output and draw progress bars despite `--color never`, `--no-progress`, or the `--quiet` used by `ty-pre-commit`; its cursor-control sequences could also erase output from earlier hooks. - Forward u
missed policy for sts in #21079
Reverts astral-sh/uv#21087, issue_comment is not supported 🤦🏼
Commit and tag information embedded in `uv --version` can remain stale after Git reference updates because the build script assumes loose shared branch refs and misses tag-only changes, worktree-private refs, chained symbolic refs, and the `reftable` backend. Watch the actual shared and worktree-local reference storage for each layout so Cargo refreshes the
third time is a charm, (now that [ost-simple-sts supports issue_comments](https://github.com/open-security-tools/ost-simple-sts/releases/tag/v0.0.5)) authorize automation for shuffling issue-context around on issue comment events
Add a minimal integration test that reproduces astral-sh/uv#21089.
When a regression-test pull request is promoted or merged while an automated fix is being prepared, the original `uv-dev` pull request closes and the fix workflow rejects it as changed. Continue only when the promoted upstream pull request preserves the verified regression branch and commit, while still rejecting unrelated closures or changed heads.
Empty PEP 508 requirements currently produce an orphaned caret after the error message, including for inline-script dependencies. Skip span formatting when the parser input is empty and update the existing parser and integration snapshots. Fixes astral-sh/uv#21089.
## Summary Previously, `uv cache size` counted every cached file independently, so hardlinks and copy-on-write clones could inflate the reported cache footprint. When `cache-physical-space` is enabled, we now count each hardlinked inode and shared physical extent once within the cache. Storage shared with files outside the cache still contributes to the cach
## Summary Relative indexes in PEP 723 scripts were resolved against the current working directory instead of the script's directory, so a script could work when ran from its own directory but fail when ran from elsewhere. This change resolves inline indexes relative to the script and also makes `uv add --script` write index paths relative to the script. It
Add a minimal integration test that reproduces astral-sh/uv#21096.