ci: add 2-day package install cooldown (supply-chain guard)#825
Merged
tchaton merged 1 commit intoMay 29, 2026
Merged
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #825 +/- ##
===================================
Coverage 81% 81%
===================================
Files 54 54
Lines 7617 7617
===================================
+ Hits 6144 6147 +3
+ Misses 1473 1470 -3 🚀 New features to boost your workflow:
|
Borda
approved these changes
May 26, 2026
deependujha
approved these changes
May 28, 2026
tchaton
approved these changes
May 29, 2026
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
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.
What does this PR do?
Adds a CI-only supply-chain guard: the resolver refuses any PyPI release published within the last 2 days, so typosquats and malicious uploads that get yanked within ~24h never land in our CI environment.
Sets
UV_EXCLUDE_NEWER: "2 days"on the uv-basedci-testingworkflow (the only uv-based workflow in this repo). pip-based workflows are out of scope for now.Follows the same pattern as pytorch-lightning#21722.
Ref: https://docs.astral.sh/uv/reference/settings/#exclude-newer