Repository navigation
Release v3.6.1: patched certifi, uv and virtualenv; require certifi>=2026.10.19 - #120
Merged
Merged
Conversation
Cut a release that ships the Dependabot security bumps merged since 3.6.0 (#112, #116, #117, #118, #119). The release build toolchain in setup-hatch still pinned virtualenv 21.7.13 and hatchling 1.32.0, because Dependabot updates uv.lock but not the pip pins inside the composite action. Sync them to the locked virtualenv 21.14.7 and the [build-system] hatchling 1.32.4 so published artifacts are built with the patched versions.
Contributor
Author
|
bugbot run |
requests takes its CA bundle from certifi, and socketdev didn't constrain it, so pip could leave consumers on a bundle that trusts the compromised eMudhra intermediate CAs. A floor rather than an exact pin, so later trust-store fixes still reach them.
v3.6.1: patched certifi, uv and virtualenv; require certifi>=2026.10.19
Contributor
Author
|
bugbot run |
David Larsen (dc-larsen)
approved these changes
Oct 21, 2026
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit a9f1ad6. Configure here.
7 tasks done
This branch was successfully deployed
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.
Summary
Release PR for 3.6.1. It ships the Dependabot security bumps merged since 3.6.0, which fix critical vulnerabilities in
certifi,uvandvirtualenv:certifiuvvirtualenvChanges
socketdev/version.pyto3.6.1.CHANGELOG.mdentry covering the security bumps, the Python 3.10 floor from fix: update security dependencies for Python 3.10+ #112, therequests>=2.33.0floor, and the build tooling maintenance.certifi>=2026.10.19.requeststakes its CA bundle from certifi, and socketdev didn't constrain it, so pip could leave consumers on a bundle that trusts the compromised eMudhra intermediate CAs. It's a floor rather than an exact pin, so later trust-store fixes still reach them. The built wheel now listsRequires-Dist: certifi>=2026.10.19..github/actions/setup-hatch(used byrelease.yml,package-check.ymlandpr-preview.yml) still installedvirtualenv==21.7.13andhatchling==1.32.0. Dependabot updatesuv.lockbut not the pip pins inside composite-action shell steps. Both pins now match the lock and[build-system](virtualenv==21.14.7,hatchling==1.32.4), so the published artifacts are built with the patched virtualenv.Notes for reviewers
uv.lockcontrols only this repo's dev and CI environment. The newcertififloor is what reaches consumers.requires-python >=3.10change from fix: update security dependencies for Python 3.10+ #112. On Python 3.9, pip keeps resolving 3.6.0.Testing
hatch==1.18.1,hatchling==1.32.4andvirtualenv==21.14.7(the new setup-hatch toolchain).twine checkpasses for both.uv lock --checkis clean.certififloor: the wheel's metadata requirescertifi>=2026.10.19, andtwine checkpasses. The integration tests needSOCKET_SECURITY_API_KEYandSOCKET_ORG_SLUG, so they were skipped locally.Public Changelog
Security release: picks up patched
certifi,uvandvirtualenvversions and requires Python 3.10 or newer. See CHANGELOG.md for details.Note
Medium Risk
Raises minimum Python and adds certifi/requests floors that affect all consumers; changes are intentional security fixes with a documented Python 3.9 pin to 3.6.0.
Overview
3.6.1 is a security-focused release that bumps the package version and documents dependency fixes in CHANGELOG.md.
For installers, the PR tightens runtime constraints:
requires-pythonis now>=3.10,requestsfloor is>=2.33.0, andcertifi>=2026.10.19is added as a direct dependency so pip pulls a CA bundle that no longer trusts the compromised eMudhra intermediates used byrequests.uv.lockis refreshed for dev/CI (includingcertifi,uv, andvirtualenvsecurity updates).Release builds align with the lockfile:
.github/actions/setup-hatchnow installshatchling==1.32.4andvirtualenv==21.14.7(matchingpyproject.toml[build-system]), so wheels/sdists published fromrelease.yml/package-check.yml/pr-preview.ymluse the patched toolchain.Reviewed by Cursor Bugbot for commit a9f1ad6. Configure here.