-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only included unyanked PyPI versions #1334
Conversation
Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci
|
Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci
|
This looks like a good enhancement, but it introduces errors to existing tests. Could you look into it? |
pypi.org allows maintainers to "yank" a PyPI release. When this happens, the PyPI backend should not include the yanked version. https://pypi.org/help/#yanked
Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci ✔️ fi-tox-mypy SUCCESS in 5m 14s |
Not every version contains yanked field, let's reflect that in the code. Signed-off-by: Michal Konečný <[email protected]>
Build succeeded. ✔️ fi-tox-mypy SUCCESS in 6m 02s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything now works as expected
Sorry I wasn't able to address this in a timely manner. Thanks for getting it resolved and merged. |
pypi.org allows maintainers to "yank" a PyPI release. When this happens, the PyPI backend should not include the yanked version.
https://pypi.org/help/#yanked