Repository navigation
chore(deps): bump certifi to 2026.10.19 - #10
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed
Follow-up to #9, which deferred certifi because the Python package's
exclude-newer = "7 days"guard kept out certifi 2026.10.19 (uploaded 2026-10-20T02:24Z) until 2026-10-27. This gives certifi its own rolling"3 days"window in the existingexclude-newer-packagemap, next to theanthropicentry. That admits 2026.10.19, the release that drops the compromised emSign roots (upstream certifi/python-certifi#437, then #440; tag 2026.10.19 is commit 662df63). It still excludes the 3-hour-old 2026.10.23, and it keeps rolling forward on its own.uv lock --upgrade-package certifithen moves certifi 2026.7.22 to 2026.10.19 inpackages/claude-toolsets-python/uv.lock. A patch changeset cuts 0.0.4 for@e2b/claude-toolsetsande2b-claude-toolsets.How I verified it
With Bun 1.4.4:
pnpm install --frozen-lockfileanduv sync --frozenpass.import certifiin the synced env reports 2026.10.19.pnpm checkpasses.pnpm test:allpasses: 24 + 41 + 88 = 153 tests, the same total as chore(deps): bump Bun to 1.4.4 #9.name/versionpair in the lock diff: the only version change is certifi.42d35340..., sdist035c1e85...).Residual risk
certifi now waits 3 days instead of 7 before a new release is picked up, so a bad certifi release would have a shorter window to be caught. Every other package keeps the 7-day guard. The wheel does not pin certifi, so this changes the locked dev, test and build environment, not users' installs or their certificate stores.