Bump black from 24.3.0 to 26.3.1 in /.devcontainer#8511
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [black](https://github.com/psf/black) from 24.3.0 to 26.3.1. - [Release notes](https://github.com/psf/black/releases) - [Changelog](https://github.com/psf/black/blob/main/CHANGES.md) - [Commits](psf/black@24.3.0...26.3.1) --- updated-dependencies: - dependency-name: black dependency-version: 26.3.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Codecov Report✅ All modified and coverable lines are covered by tests. ❌ Your project check has failed because the head coverage (82.23%) is below the target coverage (87.50%). You can increase the head coverage or adjust the target coverage.
Additional details and impacted files@@ Coverage Diff @@
## main #8511 +/- ##
==========================================
- Coverage 88.91% 82.23% -6.68%
==========================================
Files 286 286
Lines 63133 62824 -309
Branches 7915 7822 -93
==========================================
- Hits 56132 51663 -4469
- Misses 4732 8527 +3795
- Partials 2269 2634 +365 🚀 New features to boost your workflow:
|
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
ihalatci
added a commit
that referenced
this pull request
Jun 4, 2026
DESCRIPTION: Update mitmproxy fork to lift pyOpenSSL cap; re-lock to 26.2.0 (closes CVE-2026-27459, CVE-2026-27448) ## Summary Bumps the `mitmproxy` git ref in both Pipfiles from the pinned commit SHA `70bad9a3c098...` to track `citusdata/mitmproxy@main`. After [citusdata/mitmproxy#4](citusdata/mitmproxy#4) (merge of upstream `mitmproxy/mitmproxy@main`), our fork's `main` caps `pyOpenSSL<=27.0.0` (was `<=25.3.0`), unblocking the lockfile from resolving past pyOpenSSL 25.3.0. Re-locking both Pipfiles via `pipenv lock` resolves `pyopenssl` to **26.2.0**, closing all four currently-open Dependabot security alerts: | Alert | CVE | Severity | Patched version | |---|---|---|---| | [#126](https://github.com/citusdata/citus/security/dependabot/126) / [#125](https://github.com/citusdata/citus/security/dependabot/125) | [CVE-2026-27459](https://nvd.nist.gov/vuln/detail/CVE-2026-27459) ([GHSA-5pwr-322w-8jr4](GHSA-5pwr-322w-8jr4)) | **High** | `>=26.0.0` | | [#124](https://github.com/citusdata/citus/security/dependabot/124) / [#123](https://github.com/citusdata/citus/security/dependabot/123) | [CVE-2026-27448](https://nvd.nist.gov/vuln/detail/CVE-2026-27448) ([GHSA-vp96-hxj8-p424](GHSA-vp96-hxj8-p424)) | Low | `>=26.0.0` | ## Pipfile changes Single line per file, in both: - `src/test/regress/Pipfile` - `.devcontainer/src/test/regress/Pipfile` ```diff -mitmproxy = {git = "https://github.com/citusdata/mitmproxy.git", ref = "70bad9a3c098f605e5f8b25553e5db5334018ff1"} +mitmproxy = {git = "https://github.com/citusdata/mitmproxy.git", ref = "main"} ``` The `ref="main"` form is supported by pipenv for git deps; the resolved commit SHA (`df5879516a57ea780e1cc88edaf2051e1d32915f` — the merge commit of mitmproxy#4) is pinned in `Pipfile.lock`, preserving reproducibility. ## Lockfile-level changes (re-lock side-effects, no Pipfile pin changes) | Dep | Before | After | Reason | |---|---|---|---| | **mitmproxy** ref | `70bad9a3...` (==12.2.2) | `df5879516a...` (==13.0.0.dev0) | Fork tracking `main` | | **pyopenssl** | `==25.3.0` | **`==26.2.0`** | Cap lifted; fixes CVEs | | asgiref | `==3.11.0` | `==3.11.1` | Latest within range | | certifi | `==2026.2.25` | `==2026.5.20` | Latest within range | | click | `==8.3.2` | `==8.4.1` | Latest within range | | filelock | `==3.28.0` | `==3.29.0` | Latest within range | | packaging | `==26.1` | `==26.2` | Latest within range | | psycopg | `==3.3.3` | `==3.3.4` | Latest within range | | pytest-asyncio | `==1.3.0` | `==1.4.0` | Latest within range | | urwid | `==3.0.5` | `==4.0.0` | Allowed by mitmproxy main's relaxed cap | | wcwidth | `==0.6.0` | `==0.7.0` | Latest within range | Per scope direction, no other direct deps were bumped — only the security-driven `mitmproxy` ref change. Other transitive movements above are natural consequences of `pipenv lock --clear` against unchanged version constraints. ## Validation ```bash $ cd src/test/regress $ pipenv sync Installing dependencies from Pipfile.lock (416d8f)... All dependencies are now up-to-date! $ pipenv run pip show mitmproxy pyopenssl | grep -E "^Name:|^Version:" Name: mitmproxy Version: 13.0.0.dev0 Name: pyOpenSSL Version: 26.2.0 ``` Both `src/test/regress/Pipfile.lock` and `.devcontainer/src/test/regress/Pipfile.lock` are byte-identical, per the convention established in #8488 and #8547. ## Notes - Lockfiles regenerated with `pipenv lock --clear` (pipenv 2025.0.3, Python 3.12.12). - Currently-open Dependabot dependency-update bot PRs (#8525, #8526 pyasn1; #8489 werkzeug; #8510, #8511 black) target versions that the existing lockfile already satisfies — they will auto-close on next Dependabot scan without further action. - Follow-up PR on `citusdata/the-process` will regenerate the three `circleci/images/*/files/etc/requirements.txt` files (which are generated from this `Pipfile.lock` via `pipenv requirements`) once this lands. Closes #123 Closes #124 Closes #125 Closes #126 --------- 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
1 participant
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.
Bumps black from 24.3.0 to 26.3.1.
Release notes
Sourced from black's releases.
... (truncated)
Changelog
Sourced from black's changelog.
... (truncated)
Commits
c6755bbPrepare release 26.3.1 (#5046)69973fdHarden blackd browser-facing request handling (#5039)4937fe6Fix some shenanigans with the cache file and IPython (#5038)2e641d1docs: remove outdated Black Playground references (#5044)c014b22Remove unused internal code (#5041)0dae20bAdd new changelog (#5036)c5c1cbdMinor release patches (#5035)7e5a828docs: clarify relationship between Black style and PEP 8 (#5025)69705dedocs: add clearer pyproject configuration guidance (#5026)35ea679Prepare release 26.3.0 (#5032)You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.