The problem
I was updating my package's conda-forge feedstock and noticed that it failed. When I diagnosed the problem the issue was with attrs version:
aiohttp-client-cache 0.7.2 has requirement attrs<22.0,>=21.2, but you have attrs 22.1.0.
I looked into dependencies of aiohttp-client-cache and noticed that there's no upper limit for attrs in the pyproject.toml file instead the limit is set in the poetry.lock file at this line.
I wonder if this is intentional or you missed updating the poetry lock file before the new release. Also, there is no attrs upper limit in aiohttp-client-cache feedstock file at this line.
Expected behavior
If the upper limit is intentional pip check shouldn't fail.
Steps to reproduce the behavior
Check the log of my package's feedstock repo here.
Workarounds
If the upper limit is intentional both the meta.yml and pyproject.toml files need to be updated.
Environment
- aiohttp-client-cache version:
0.7.2
- Python version: conda-forge feedstock CI
- Platform: conda-forge feedstock CI
The problem
I was updating my package's conda-forge feedstock and noticed that it failed. When I diagnosed the problem the issue was with
attrsversion:I looked into dependencies of
aiohttp-client-cacheand noticed that there's no upper limit forattrsin thepyproject.tomlfile instead the limit is set in thepoetry.lockfile at this line.I wonder if this is intentional or you missed updating the poetry lock file before the new release. Also, there is no
attrsupper limit inaiohttp-client-cachefeedstock file at this line.Expected behavior
If the upper limit is intentional
pip checkshouldn't fail.Steps to reproduce the behavior
Check the log of my package's feedstock repo here.
Workarounds
If the upper limit is intentional both the
meta.ymlandpyproject.tomlfiles need to be updated.Environment
0.7.2