Sync Citus image requirements to close pyOpenSSL CVE alerts#219
Open
ihalatci wants to merge 1 commit into
Open
Sync Citus image requirements to close pyOpenSSL CVE alerts#219ihalatci wants to merge 1 commit into
ihalatci wants to merge 1 commit into
Conversation
Regenerates the four image requirements files from Citus's regenerated Pipfile.lock on citusdata/citus#8596, which lifts the mitmproxy fork's pyOpenSSL cap and pulls pyOpenSSL forward to a non-vulnerable release. Tester images (pgupgradetester, failtester, citusupgradetester), regenerated via 'pipenv requirements > requirements.txt': pyopenssl 25.3.0 -> 26.2.0 mitmproxy (fork ref) 70bad9a3 -> df5879516 asgiref 3.11.0 -> 3.11.1 certifi 2026.2.25 -> 2026.5.20 click 8.3.2 -> 8.4.1 filelock 3.28.0 -> 3.29.0 packaging 26.1 -> 26.2 psycopg 3.3.3 -> 3.3.4 pytest-asyncio 1.3.0 -> 1.4.0 urwid 3.0.5 -> 4.0.0 wcwidth 0.6.0 -> 0.7.0 Stylechecker, regenerated via 'pipenv requirements --dev-only': click 8.3.2 -> 8.4.1 packaging 26.1 -> 26.2 pathspec 1.0.4 -> 1.1.1 platformdirs 4.9.6 -> 4.10.0 These mirror the natural transitive movements from re-locking the Citus Pipfile after the mitmproxy ref switched to track main. No new top-level packages added or removed; no dropped pins. Verified: clean Python 3.12 venv installs each set without errors and 'pip check' reports no broken requirements. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
Regenerates the four Citus image requirement files from the updated
Citus
Pipfile.lockproduced by citusdata/citus#8596,which lifts the citusdata/mitmproxy
fork's
pyOpenSSLcap and pullspyOpenSSLforward past two CVEs.Pairs with:
What changed
Three tester images, regenerated via
pipenv requirements > requirements.txt(byte-identical across
pgupgradetester,failtester,citusupgradetester):pyopensslmitmproxy(fork ref)70bad9a3df5879516asgirefcertificlickfilelockpackagingpsycopgpytest-asynciourwidwcwidthStylechecker image, regenerated via
pipenv requirements --dev-only > requirements.txt(natural transitive drift from re-locking; no top-level dev deps changed):
clickpackagingpathspecplatformdirsNo new top-level packages added or removed; no dropped pins.
Notes
Same workflow as #214: regenerated artifacts following the instructions
in the file headers rather than hand-edited. Header PR reference bumped
#8547→#8596to track the source lockfile.Verification
with
pip install -r ...; both completed without resolver errors.pip checkreports no broken requirements for both sets.pyOpenSSLversion is26.2.0(closes CVE-2026-27459HIGH and CVE-2026-27448) and the installed
mitmproxyresolves to thepost-merge fork ref
df5879516.