Remove uv.lock freshness check, add weekly update workflow #7035
+77
−18
Conversation
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
- Remove check-lock-freshness job from PR CI workflow - Add scheduled weekly workflow to update uv.lock automatically Closes PolicyEngine#7034 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Closes #7034
Remove the strict
uv.lockfreshness check from PR CI and replace it with a weekly scheduled workflow.Changes
check-lock-freshnessjob from.github/workflows/pr.yaml.github/workflows/weekly-uv-lock.yaml- runs every Wednesday at 5 PM EST to update dependencies automaticallyReason
The current check is too strict. A weekly scheduled script will keep the lock file up to date instead.
🤖 Generated with Claude Code