chore: min age for dependencies#1218
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
WalkthroughThe PR adds version-age constraints to dependency resolution across the codebase: ChangesDependency Version Constraints
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Not ideal - it updated all the existing dependencies |
📊 Coverage ReportOverall Coverage: 92% Diff: origin/main...HEADNo lines with coverage information in this diff.
|
There was a problem hiding this comment.
Code Review
This pull request implements dependency age constraints by adding exclude-newer to uv configurations and min-release-age to npm settings. It also removes peer dependency flags from package-lock.json and adjusts the asyncio fixture scope in pytest.ini. Feedback indicates that the npm min-release-age value is incorrectly set to 7 seconds instead of 7 days, and the [tool.uv] settings in workspace member files are redundant as they are inherited from the root configuration.
6dc43a4 to
ad3a042
Compare
| "resolved": "https://registry.npmjs.org/@babel/core/-/core-7.29.0.tgz", | ||
| "integrity": "sha512-CGOfOJqWjg2qW/Mb6zNsDm+u5vFQ8DxXfbM09z69p5Z6+mE1ikP2jUXw+j42Pf1XTYED2Rni5f95npYeuwMDQA==", | ||
| "license": "MIT", | ||
| "peer": true, |
There was a problem hiding this comment.
this thing comes and goes
What does this PR do?
Add
exclude-newerinpyproject.tomlfiles so thatuv addinstalls dependencies not newer than a certain age (7 days) to decrease the risk of installing attacked deps.Also added
min-release-ageto do the same fornpm i- the flag is relatively recent innpm, so you neednpm >= 11.x. Update yournpmwithnpm install -g npm@latest.You also need to run
uv sync.Checklists