uv lock doesn't indicate that it has updated the lock file

[zanieb]

The output is just "Resolved ... packages in ...", maybe we should indicate that we've updated the file or locked dependencies?

Even the verbose output doesn't show any indication of updating the lock file.

[zanieb]

It'd probably be nice to know if the file was left unchanged or if we updated it.

[kidrahahjo]

I agree. Would it also make sense to give a brief description of what changed (it can be enabled by default and users would be able to disable it using a --no-summary flag)?

The output command can be

package	old version	new version	action
xyz		1.0.0	ADDED
abc	0.0.1		DELETED
efg	0.1.0	0.1.1	UPDATED

Although this has a downside of a huge output on initial lock creation (and probably more things). Apart from this, for a usual development workflow, teams can always check the diff to see what has changed.

[zanieb]

Cargo has a nice example here

Updating lockfile...
    Updating uv v0.2.11 (/Users/zb/workspace/uv/crates/uv) -> v0.2.12
    Updating uv-version v0.2.11 (/Users/zb/workspace/uv/crates/uv-version) -> v0.2.12
note: pass `--verbose` to see 102 unchanged dependencies behind latest

[kidrahahjo]

Yeah, this is a nice inspiration.

I see cargo update --verbose is way less verbose than uv lock --verbose. Do you think we should transition the current verbose flag to very verbose (-vv) and have the verbose flag (-v) for a pretty verbose output?

[zanieb]

We have a tracking issue for that at #1569, we need to do quite a bit of work around our tracing output levels eventually it's just not as high of a priority as the rest of the interface right now.