Skip to content

uv-lock hook can pass with an outdated lockfile when UV_FROZEN=1 #70

Description

@jfra1397

With UV_FROZEN=1, the uv-lock hook can pass even when the lockfile is outdated.

This caused problems for us in CI, where UV_FROZEN=1 is commonly set: a change that should have required a lockfile update was not caught.

Expected: Hook fails when lockfile is outdated.
Actual: Hook does not update the lockfile and does not fail, so lockfile drift can pass unnoticed.
Workaround: Set UV_FROZEN=0 for uv-lock hook execution only.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    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