Skip to content

[C4] uv.lock committed but unused in CI; pip resolves floating deps #294

Description

@DsThakurRawat

Labels: ci, packaging, priority:medium
File: uv.lock (580 KB, committed), pytest.yml:39 (pip install -e), cache keyed on unpinned pyproject.toml

Description. Every install workflow uses pip install -e (not uv sync --locked); deps are almost all floors (torch>=2.1.0, transformers>=4.40,<5.4). The committed lockfile is never used.

Why it matters. CI resolves fresh versions on cache miss, so a breaking upstream release turns CI red with no code change, and green CI doesn't reproduce what a customer's pip install gets. The lockfile that would prevent this is dead weight drifting from reality.

Tasks.

  • Either install from uv.lock in CI (uv sync --locked) + add a lock-freshness check, or delete the unused lockfile. Pick one source of truth.

Dedup. Not covered.

Metadata

Metadata

Assignees

No one assigned

    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