Skip to content

fix(deps): exempt certifi and uv from the uv cooldown - #1380

Draft
brendan-priorlabs wants to merge 2 commits into
mainfrom
brendan/q-2026-10-22_1433-certifi-fallout-remediation-plan
Draft

brendan-priorlabs wants to merge 2 commits into
mainfrom
brendan/q-2026-10-22_1433-certifi-fallout-remediation-plan

Conversation

@brendan-priorlabs

Copy link
Copy Markdown
Contributor

Follow-up to the eMudhra CA fix. This repo sets a uv cooldown (exclude-newer) but didn't exempt certifi and uv from it. As a result, uv lock/uv sync refuses certifi ≥ 2026.10.19 and uv ≥ 0.13.4 until the cooldown expires (~Oct 26–27). Local environments stay on the vulnerable versions, and syncing with -P certifi fails to resolve.

This adds certifi = "0 days", uv = "0 days" to exclude-newer-package, matching tabpfn-client, tabpfn-extensions and tabpfn-server.

The original fix PR missed this because this repo doesn't commit a uv.lock (or the lock was patched in place), so the fixer saw nothing to relock.

Tested (TabPFN): uv lock -P certifi -P uv with this change moves certifi 2025.7.14 → 2026.10.23 and uv 0.11.18 → 0.13.5. Without it, the resolution fails.

🤖 Generated with Claude Code

brendan-priorlabs and others added 2 commits October 23, 2026 17:05
Without this, exclude-newer blocks the eMudhra-fixed certifi (>=2026.10.19)
and uv (>=0.13.4) until the cooldown expires.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
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.

1 participant