Advance mitmproxy pin to unblock security dependency sync - #8840
Closed
ibrahim halatci (ihalatci) wants to merge 1 commit into
Closed
Advance mitmproxy pin to unblock security dependency sync#8840ibrahim halatci (ihalatci) wants to merge 1 commit into
ibrahim halatci (ihalatci) wants to merge 1 commit into
Conversation
Consume the fork revision permitting patched cryptography, h2, and tornado versions, including OpenSSL 4 protocol-probe compatibility. Preserve existing resolved versions so the security-sync workflow generates the coordinated dependency and image updates. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8840 +/- ##
==========================================
- Coverage 88.73% 88.73% -0.01%
==========================================
Files 289 289
Lines 65012 65012
Branches 8203 8204 +1
==========================================
- Hits 57690 57688 -2
- Misses 4952 4954 +2
Partials 2370 2370 🚀 New features to boost your workflow:
|
Contributor
Author
|
Superseded by #8841, which includes this mitmproxy pin change together with the generated security dependency updates. The coordinated image requirements are in citusdata/the-process#249; that PR should merge first so its post-merge workflow advances the Citus PR to released images. Closing only this duplicate pin-only PR. |
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
Advance the Citus mitmproxy fork pin to the commit from citusdata/mitmproxy#5 in both regression-test Pipfiles and their lock metadata.
The updated fork adds cap support for:
cryptography==50.0.0h2==4.4.1tornado==6.5.8This is intentionally a metadata-only minimal change: current package versions remain pinned. Once this PR merges, run
dependency-security-syncincitusdata/the-processto generate the actual patched Citus lockfiles and test-image requirements as coordinated PRs.Validation
The current
.github/scripts/security_sync.pyfromcitusdata/the-processwas run against all 14 current Citus Dependabot alerts in WSL Ubuntu 22.04 with Python 3.12, resolving the unpublished fork commit locally through a temporary Git URL rewrite.tornado,h2, andcryptographyall reported['applied', 'applied']blocked=[]pipenv verifysucceededpip checksucceededmitmdump --versionstarted successfully with OpenSSL 4.0.1No workflow code, package versions, tests, or build tools are changed here.