Skip to content

uv sync/lock --upgrade-package and --upgrade-group accept non-existent names without warning or error #18939

Description

@DhavalGojiya

Summary

uv sync and uv lock appear to silently accept non-existent package or group names when using --upgrade-package or --upgrade-group.

Even if the provided package or group does not exist in the project dependencies, the command completes successfully and reports everything as resolved/up to date.

This can be confusing because it may hide typos or incorrect package/group names.

Reproduction

Image

Platform

Linux 6.17.0-20-generic x86_64 GNU/Linux

Version

uv 0.11.5 (x86_64-unknown-linux-gnu)

Python version

Python 3.14.3

Metadata

Metadata

Assignees

Labels

breakingA breaking changebugSomething isn't working

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions