-
Notifications
You must be signed in to change notification settings - Fork 180
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
Downgrade packaging. #1270
Downgrade packaging. #1270
Conversation
pypa/packaging#321 removed support for parsing legacy PyPI versions, which we needed to make our version enumeration/sorting work. This upgrade happened in f968260, but somehow we didn't notice this breakage.
Also CC @di if there are better workarounds for us here other than downgrading? |
I noticed this from https://github.com/pypa/advisory-database/actions/runs/4878347479/jobs/8703902390
There were a small number of instances on prod over the past 30 days, but it somehow slipped through the cracks for us. |
So how did we eventually notice the breakage and what needs to be done differently so we don't miss it? (i.e. what's the mini-postmortem learning here?) |
I noticed separately via https://github.com/pypa/advisory-database/actions/runs/4878347479/jobs/8703902390 The error was on our error dashboard: https://pantheon.corp.google.com/errors/detail/CNGT29fs5Oj_DA;service=gke_instances?project=oss-vdb but we did not notice it :( |
You can use https://pypi.org/p/packaging-legacy as a drop-in replacement. |
Ah awesome, thanks Dustin! |
pypa/packaging#321 removed support for parsing legacy PyPI versions, which we needed to make our version enumeration/sorting work.
This upgrade happened in
f968260, but somehow we didn't notice this breakage.