chore(deps): use 3-day exclude-newer window#5742
Merged
Merged
Conversation
Aligns the root workspace with the per-package pyprojects, which already use `exclude-newer = "3 days"`. The fixed 2026-04-27 cutoff blocks legitimate dependency bumps (e.g. daytona ~=0.171 in #5740) without adding meaningful protection — the relative window still includes the security patches that motivated the original pin.
iris-clawd
approved these changes
May 7, 2026
Contributor
iris-clawd
left a comment
iris-clawd
left a comment
There was a problem hiding this comment.
LGTM — clean and straightforward. Aligns root exclude-newer with the rolling 3-day window already used by all sub-packages. No runtime changes, just unblocks future dependency bumps (like #5740). 💬 384
- gitpython >=3.1.49 for GHSA-v87r-6q3f-2j67 (newline injection in config_writer().set_value() enables RCE via core.hooksPath). - python-multipart >=0.0.27 for GHSA-pp6c-gr5w-3c5g (DoS via unbounded multipart part headers). Both surfaced via pip-audit on this branch.
iris-clawd
approved these changes
May 7, 2026
Contributor
iris-clawd
left a comment
iris-clawd
left a comment
There was a problem hiding this comment.
Re-reviewed after second commit. Security pin bumps look good — gitpython 3.1.49 (GHSA-v87r-6q3f-2j67, RCE via newline injection) and python-multipart 0.0.27 (GHSA-pp6c-gr5w-3c5g, DoS via unbounded headers). Both are override-only, no runtime changes. Still LGTM ✅ 💬 385
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.
Summary
[tool.uv] exclude-newerfrom the fixed2026-04-27to"3 days", matching the per-package pyprojects (lib/crewai,lib/crewai-tools,lib/crewai-files,lib/devtoolsall use"3 days"already).Why
The fixed cutoff blocks legitimate dependency bumps. Concretely, #5740 bumps
daytona ~=0.140.0→~=0.171, butdaytona 0.171was first published 2026-04-30, after the cutoff, souv syncfails to resolve.Test plan
uv sync --all-groups --all-extras --no-install-projectsucceeds locallyNote
Medium Risk
Moderate risk because it changes dependency resolution policy and updates pinned transitive tooling deps (
gitpython,python-multipart), which could affect reproducibility or CI if the lockfile is regenerated.Overview
Switches root
pyproject.tomltool.uv.exclude-newerfrom a fixed timestamp to a rolling"3 days"window, and updates accompanying comments to reflect current security pin rationale.Refreshes
override-dependencies/uv.lockto incorporate security-related minimums, including bumpingpython-multipartto0.0.27and adding/upgradinggitpythonto>=3.1.49,<4(lock now resolvesgitpython3.1.49), plus lockfile metadata updates (exclude-newer-span).Reviewed by Cursor Bugbot for commit e559d03. Bugbot is set up for automated code reviews on this repo. Configure here.