Skip to content

lock_requires_python flakes when a new pre-releases version is addeded #13867

@zanieb

Description

@zanieb
    running 1 test
    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Snapshot Summary ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    Snapshot: lock_requires_python
    Source: crates/uv/tests/it/lock.rs:3668
    ────────────────────────────────────────────────────────────────────────────────
    Expression: snapshot
    ────────────────────────────────────────────────────────────────────────────────
    -old snapshot
    +new results
    ────────────┬───────────────────────────────────────────────────────────────────
       15    15 │           pygls>1.3.0
       16    16 │        cannot be used, we can conclude that pygls>=1.1.0 cannot be used.
       17    17 │       And because your project depends on pygls>=1.1.0, we can conclude that your project's requirements are unsatisfiable.
       18    18 │ 
       19       │-      hint: Pre-releases are available for `pygls` in the requested range (e.g., 2.0.0a3), but pre-releases weren't enabled (try: `--prerelease=allow`)
             19 │+      hint: Pre-releases are available for `pygls` in the requested range (e.g., 2.0.0a4), but pre-releases weren't enabled (try: `--prerelease=allow`)
       20    20 │ 
       21    21 │       hint: The `requires-python` value (>=3.7) includes Python versions that are not supported by your dependencies (e.g., pygls>=1.1.0,<=1.2.1 only supports >=3.7.9, <4). Consider using a more restrictive `requires-python` value (like >=3.7.9, <4).
    ────────────┴───────────────────────────────────────────────────────────────────
    Stopped on the first failure. Run `cargo insta test` to run all snapshots.
    test lock::lock_requires_python ... FAILED

Metadata

Metadata

Assignees

No one assigned

    Labels

    ci-flakeRelated to internal CI flakes

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions