Skip to content

A reminder about upper pins #5824

@ilan-gold

Description

@ilan-gold

I think a reminder about making patch PRs would be helpful.

In conda-forge/anndata-feedstock#63 I upper pinned pandas<3 without realizing that conda would automatically backtrack until the upper pin was not there if another package wants pandas>=3 for some reason i.e., instead of giving pandas<3, it goes to an earlier version of our package without the pin and then installs pandas>=3 with that. But of course, this behavior produced broken environments for people where older versions of our package are incompatible with new versions of pandas.

In general, I'd be curious if there is ever a case where you wouldn't want this upper bound to be automatically backported in conda-forge/conda-forge-repodata-patches-feedstock#1172. It seems like if your latest build is broken with a new release, so is everything before it (unless you accidentally support it somehow in a previous release).

But even without an automatic patch PR maker for repodata-patches, I think a reminder in the message in conda-forge/anndata-feedstock#63 would be nice!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions