Summary

With the following minimal reproducible example, running uv lock does not change the contents of uv.lock. However, running uv lock --locked reports error: The lockfile at `uv.lock` needs to be updated, but `--locked` was provided. To update the lockfile, run `uv lock`. Running uv lock as suggested still does not change the lockfile.

I would expect the two commands to be consistent, i.e., uv lock --locked not to report that the lockfile needs to be updated when uv lock doesn't update it and indeed it doesn't need any updates.

pyproject.toml:

[project]
name = "test"
version = "0"

[tool.uv.workspace]
members = ["test2"]

[tool.uv.sources]
test2 = { workspace = true }

test2/pyproject.toml:

[project]
name = "test2" 
dynamic = ["version"]

[project.optional-dependencies]
foo = []
bar = []

all = ["test2[foo,bar]"]

uv.lock:

version = 1
requires-python = ">=3.11"

[manifest]
members = [
    "test",
    "test2",
]

[[package]]
name = "test"
version = "0"
source = { virtual = "." }

[[package]]
name = "test2"
source = { virtual = "test2" }

[package.metadata]
requires-dist = [{ name = "test2", extras = ["bar", "foo"], marker = "extra == 'all'", virtual = "test2" }]

I couldn't reduce this to a smaller example, i.e., removing any of the optional dependencies of test2 cause the bug to be not reproduced. Merging the contents of test/pyproject.toml into the root pyproject.toml also cause the bug to disappear.

I couldn't find an exact duplicate of this bug, but sorry if I missed something.

Platform

Darwin 23.6.0 arm64

Version

uv 0.5.21 (Homebrew 2025-01-17)

Python version

Python 3.11.10