Skip to content

uv self update is blocked by required-version #10355

@tpgillam

Description

@tpgillam

Initial state:

> uv --version
uv 0.5.14
> cat pyproject.toml | grep required-version
required-version = ">=0.5.15"
> uv sync
error: Required version `>=0.5.15` does not match the running version `0.5.14`

All fine so far, but:

> uv self update
error: Required version `>=0.5.15` does not match the running version `0.5.14`

so the obvious way to fix the uv-is-too-old problem doesn't work :) Naturally this is easily worked around by cd-ing to a different directory, but it seems likely to me that blocking uv self wasn't intended!

I've also tried the same thing after upgrading to uv 0.5.15, and changing required-version to >=0.5.16, just to check whether the issue had been fixed already.

(Aside: it might also be useful if the error message said "Required uv version...". I can imagine a user who didn't add the uv version bound constraint potentially being confused about what is actually binding.)

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions