Skip to content

conda_vendor --refresh-pins stays silent when the pinned release lost a wheel #2028

Closed

Description

@JarryShaw

Describe the bug
util/conda_vendor.py refresh() still makes no note when the newest release with a wheel for every conda Python is older than the pin, i.e. the pinned release itself has lost a wheel. The pin stays as it is, and --refresh-pins passes silently. #2026 fixes the related case where no release qualifies at all, and deliberately leaves this one out.

Reproduction
Reading refresh() at #2026's head: the branch newest is not None and target is None covers both "the pin is still the newest" (correct, silent) and newest < pin.version (stuck, silent).

Expected behavior
A ::warning that names the pin and the newest release that still qualifies, with the step still passing, as #2026 does for the no-release case.

System information

Additional context
Raised in #2026's cross-review. It touches the same function, so it waits for #2026 to land.

Activity

  1. added
    bugIssues reporting a defect (set by the bug report template; a default, not an assessment)
    ciPull requests that change CI or workflow configuration (ci: subject prefix)
    blockedDeferred pending another issue or decision; see the last comment for what unblocks it
    on Oct 22, 2026
  2. moved this to Blocked in PyPCAPKiton Oct 22, 2026
  3. JarryShaw commented on Oct 22, 2026

    @JarryShaw
    OwnerAuthor

    Unblocked: #2026 landed as 4930a7aae. A fix is starting now.

  4. added
    wipWork in flight - a covering PR is open or an agent is actively on it
    and removed
    blockedDeferred pending another issue or decision; see the last comment for what unblocks it
    on Oct 22, 2026
  5. moved this from Blocked to WIP in PyPCAPKiton Oct 22, 2026
  6. removed
    wipWork in flight - a covering PR is open or an agent is actively on it
    on Oct 22, 2026
  7. added this to the PyPCAPKit v1.5 milestone on Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIssues reporting a defect (set by the bug report template; a default, not an assessment)ciPull requests that change CI or workflow configuration (ci: subject prefix)

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions