Confused about updating packages

[lucharo]

Question

Hi, the other day I was working on my project, managed by uv. I wanted to upgrade my polars version to the latest version. I ran uv add -U polars from a folder not in the root of my project (so pyproject.toml) wasn't in that folder, the environment updated succesfully but the changes weren't reflected in my pyproject.toml). I then navigated to the root of the project and ran the same command again, still nothing happened. Then I ran uv add "polars==1.24.0" and finally the pyproject.toml, is this expected?

I would have assumed that uv add -U polars would have updated my environment and my pyproject.toml from wherever it had been executed.

Platform

Darwin 24.3.0 arm64

Version

uv 0.5.4 (c62c83c 2024-11-20)

[zanieb]

Sounds like you're looking for #6794

It does sound reasonable to bump the lower bound in uv add -U polars though 🤔

cc @konstin

[sglbl]

Related 11509 . I agree and I thought the same thing that this already existed.

[konstin]

Agreed that this is unintuitive.

For context, this is currently happening because we treat --upgrade as a (basically global) lockfile-only option, so uv add --upgrade foo says "add foo to pyproject.toml (if it doesn't exist) and update the versions in the lockfile" instead of the expected "add the latest lower bound of foo to pyproject.toml and update the versions in the lockfile".