add 1 week dependency cooldown for uv#599
Merged
Merged
Conversation
moritz-gross
added
enhancement
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
the recent bug in a python package regarding Traditional Chinese character encodings got me thinking about how to manage Python packages generally.
From what I have observed generally, it's a good idea to add a waiting period of a week or so for new package versions, which should avoid most cases where packages have been infiltrated by malware, ship really bad bugs, or similar stuff. This doesn't solve all problems of course, but it's a low effort step that could maybe be really helpful at some point.
Similar logic would apply to Rust crates I think, so maybe we should look into it there at some point as well.