Skip to content

chore: replace expired static dates in uv exclude-newer-package confi…#4598

Closed
rakdutta wants to merge 1 commit intomainfrom
fix/issue-4566-replace-hardcoded-dates
Closed

chore: replace expired static dates in uv exclude-newer-package confi…#4598
rakdutta wants to merge 1 commit intomainfrom
fix/issue-4566-replace-hardcoded-dates

Conversation

@rakdutta
Copy link
Copy Markdown
Collaborator

@rakdutta rakdutta commented May 5, 2026

closes #4566

Replaces expired hardcoded dates in [tool.uv.exclude-newer-package] with false to properly exempt trusted packages from the global 10-day exclude-newer constraint.

Problem: Static timestamps (2026-04-09 to 2026-04-22) have all expired, preventing packages from receiving updates and requiring manual maintenance.

Solution: Set all 14 packages to false per uv docs to exempt them entirely from the global constraint.

Affected packages: cpex-* (6), authlib, cryptography, Mako, python-multipart, langchain-core, langchain-openai, langsmith, uv

Benefits: No manual date maintenance, security patches applied automatically, preserves original intent.

…g with false to exempt trusted packages (fixes #4566)

Signed-off-by: Rakhi Dutta <rakhibiswas@yahoo.com>
@rakdutta
Copy link
Copy Markdown
Collaborator Author

rakdutta commented May 6, 2026

Closing in favor of the date-based approach per team discussion. PR #4596 demonstrates the pattern of bumping dates for specific releases. Long-term fix will be addressed in #4560

@rakdutta rakdutta closed this May 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CHORE]: Replace hardcoded dates in tool.uv.exclude-newer-package with false

1 participant