Can 0.2.1.post1 be yanked?
@emilykl is already working on this.
Since Oct 1, 2025.
- Dominant language
- Python
- Stars
- 498
- Forks
- 62
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 2
Description
With tools that perform universal resolution instead of platform-specific resolution, such as uv, tools pick up 0.2.1.post1 instead of 0.2.1 for a >=0.2, <0.3 pin (or poetry's ^0.2) and then fail to install on most machines.
While this release is old and it has been fixed on newer versions, there are still a number of projects that depend on 0.2.x, which makes this problem show up here (https://github.com/plotly/Kaleido/issues/292) and regularly in the uv bug tracker (https://github.com/astral-sh/uv/issues?q=is%3Aissue%20kaleido). Would it be possible to yank 0.2.1.post1 to prevent this user confusion?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.