Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unpublished releases not reverted
See original GitHub issueBasically, I have a project that depends on pyyaml.
PyYAML released version 4.1, which generated a PR in my project. However, the developers subsequently determined that there were issues with their release, and unpublished the release.
This means that the most recent version available is now 3.12, so installs that use my requirements.txt file now fail.
It seems like since pyup is already tracking releases, it should be able to handle the case where a more recent release is unpublished due to security/integrity/bugs/whatnot, and PR the appropriate reversions.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@fake-name @edmorley I am working on a system handle unpublished releases and should have it in production in the next few days. Thanks for your patience here!
@fake-name sorry for taking so long to get back to you.
My assumption is that you are probably not suffering from this anymore for such specific packages. Anyway, this is still a valid concern. We must be on top of unpubilshed or removed packages as you said. Unfortunately, that is not a very common and good practice. Project maintainers are supposed to republish a fixed, even if reverted, version when that happens.
Anyway, that does not invalidate your request here.