Skip to content

uv lock warning suggests non-existent --no-frozen flag #19290

@pdecat

Description

@pdecat

Summary

When UV_FROZEN=1 is set (or frozen is set in workspace configuration), running uv lock emits a hint that doesn't work:

UV_FROZEN=1 uv lock
warning: The lockfile at `uv.lock` was only checked for validity, not whether it is up-to-date, because `UV_FROZEN=1` was provided; use `--no-frozen` or `--check` instead
UV_FROZEN=1 uv lock --no-frozen
error: unexpected argument '--no-frozen' found

  tip: a similar argument exists: '--frozen'

Usage: uv lock --check-exists

For more information, try '--help'.

That hint comes from https://github.com/astral-sh/uv/blob/0.11.9/crates/uv/src/commands/project/lock.rs#L233

Platform

Linux 7.0.0-14-generic x86_64

Version

uv 0.11.8 (x86_64-unknown-linux-musl)

Python version

Python 3.14.4

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions