Skip to content

deps: bump the runtime group across 1 directory with 6 updates - #465

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/runtime-f154f57835
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/runtime-f154f57835

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Updates the requirements on pybatfish, pandas, ollama, fastapi, uvicorn and python-multipart to permit the latest version.
Updates pybatfish from 2025.7.7.2423 to 2026.9.17.3748

Release notes

Sourced from pybatfish's releases.

Pybatfish 2026.09.17

What's Changed

  • Fix an issue with the requests timeout added in the prior release. Pybatfish would time out and re-upload large snapshots batfish/pybatfish#994

Full Changelog: batfish/pybatfish@v2026.08.19...v2026.09.17

Pybatfish 2026.08.19

What's Changed

New Contributors

Full Changelog: batfish/pybatfish@v2025.07.07...v2026.08.19

Commits

Updates pandas to 3.1.1

Release notes

Sourced from pandas's releases.

pandas 3.1.1

We are pleased to announce the release of pandas 3.1.1. This is a patch release in the 3.1.x series and includes some regression fixes and bug fixes. We recommend that all users of the 3.1.x series upgrade to this version.

See the full whatsnew for a list of all the changes.

The release can be installed from PyPI:

python -m pip install --upgrade pandas==3.1.*

Or from conda-forge

conda install -c conda-forge pandas=3.1

Please report any issues with the release on the pandas issue tracker.

Thanks to all the contributors who made this release possible.

Commits
  • 3dcc6fb RLS: 3.1.1
  • 01560e3 Backport PR #71896 on branch 3.1.x (DOC: cleanup 3.1.1 whatsnew) (#71898)
  • 49709c4 [backport 3.1.x] BUG: ffill/bfill on Arrow arrays without NA returns a view o...
  • 55089f8 Backport PR #71025 on branch 3.1.x (BUG: \s and \S in str regex methods missi...
  • eea23d0 Backport PR #71782 on branch 3.1.x (BUG: py.path.local treated as an open buf...
  • e427eb5 [backport 3.1.x] DOC: avoid system-ui in default font-family for the docs (re...
  • 3120a57 Backport PR #71572 on branch 3.1.x (BLD: don't include moments_simd.hpp in mo...
  • 378620e Backport PR #71865 on branch 3.1.x (REGR: ensure map() with datetime-like dty...
  • ceca8cb Backport PR #71495 on branch 3.1.x (BUG: support python-dateutil 3.0 tzfile (...
  • 68fc76e Backport PR #71661 on branch 3.1.x (CI: Remove install requirement-dev.txt sm...
  • Additional commits viewable in compare view

Updates ollama to 0.6.3

Release notes

Sourced from ollama's releases.

v0.6.3

What's Changed

New Contributors

Full Changelog: ollama/ollama-python@v0.6.2...v0.6.3

Commits
  • 8785556 types/client: relax think type to support model-defined thinking levels (#744)
  • ed18cea feat: add System One API support (#749)
  • b28b1e8 readme: update to use gemma 4 and format (#740)
  • fa85099 types: make Image path extension check case-insensitive (#696)
  • 25b9329 fix: handle multiple tool calls in tools examples (#634)
  • 3c5a26a client: widen sync generate think type to accept string levels (#697)
  • See full diff in compare view

Updates fastapi to 0.163.1

Release notes

Sourced from fastapi's releases.

0.163.1

FastAPI includes an official skill that helps coding agents use new features and recommended patterns for your installed version. Install it with uvx library-skills in your project. See Develop with AI.

Fixes

Commits

Updates uvicorn to 0.54.0

Release notes

Sourced from uvicorn's releases.

Version 0.54.0

📨 Send metadata after the response body

uvicorn 0.54.0 adds response trailers and 103 Early Hints to its experimental HTTP/2 implementation through zttp.

uv add uvicorn==0.54.0 "zttp>=0.0.34"
  • Send HTTP/2 response trailers (#3146). The ASGI http.response.trailers extension lets applications send metadata, such as checksums, after the response body. Clients must send TE: trailers to receive them. Multiple trailer messages are combined before completing the response.
  • HTTP/2 remains experimental and opt-in. Enable it with --http zttp --http2. Upgrade-based h2c and WebSockets over HTTP/2 remain unsupported.

💡 Hint at resources before the final response

  • Send 103 Early Hints over HTTP/2 (#3137). Applications can use the ASGI http.response.early_hint extension to send resource hints before the final response. Each supplied link becomes a separate Link header.

Full changelog: 0.53.0...0.54.0

Changelog

Sourced from uvicorn's changelog.

0.54.0 (September 24, 2026)

HTTP/2 support remains experimental. Install zttp>=0.0.34 and enable it with --http zttp --http2.

Added

  • Add HTTP/2 response trailers through the ASGI http.response.trailers extension. Clients must send TE: trailers to receive them (#3146)
  • Add HTTP/2 103 Early Hints through the ASGI http.response.early_hint extension (#3137)

0.53.0 (September 14, 2026)

This release adds experimental HTTP/2 support through zttp. Enable it with --http zttp --http2. Upgrade-based h2c and WebSockets over HTTP/2 are not supported.

Added

  • Add experimental HTTP/2 support through zttp (#2982, #3101)
  • Add support for zuvloop (#3104)

Fixed

  • Handle comma-separated, case-insensitive Connection: close tokens across HTTP implementations (#3103)
  • Trust IPv6 loopback in the default FORWARDED_ALLOW_IPS value (#3119)
  • Cancel the HTTP keep-alive timer when upgrading to WebSocket (#3107)

0.52.4 (August 18, 2026)

Fixed

  • Remove duplicate Date headers from accepted WebSocket handshakes with websockets-sansio (#3078)

0.52.3 (August 13, 2026)

Changed

  • Update zttp to 0.0.24 and use its combined receive path, improving HTTP/1.1 request parsing performance (#3067)

0.52.2 (August 13, 2026)

Fixed

  • Update zttp to 0.0.22, fixing bodyless request receives and improving HTTP/1 request parsing performance (#3063)

0.52.1 (August 1, 2026)

Fixed

  • Complete the closing handshake on server-initiated WebSocket closes in the websockets-sansio and wsproto implementations, waiting for the client's close reply with a 10 second timeout instead of resetting the connection (#3053)
  • Add missing write flow control to the websockets-sansio implementation, preventing data truncation on server-initiated closes with large in-flight payloads (#3048)
  • Handle connection loss while a WebSocket write is waiting on backpressure (#3050)

... (truncated)

Commits

Updates python-multipart to 0.0.33

Release notes

Sourced from python-multipart's releases.

Version 0.0.33

🛡️ Safer form parsing

This release lets you cap URL-encoded form fields as they stream in, and fixes several upload and decoding edge cases. It also drops Python 3.10 and adds Python 3.15.

pip install python-multipart==0.0.33
  • Limit URL-encoded fields while streaming (#333). The new opt-in MAX_FIELDS and MAX_FIELD_SIZE options for FormParser raise FormParserError before oversized data is buffered. Both default to no limit, and multipart forms are unaffected.
  • Nameless uploads no longer crash when spilled to disk (#343). Uploads without a filename used to raise AttributeError when UPLOAD_KEEP_EXTENSIONS or UPLOAD_KEEP_FILENAME was set.
  • UPLOAD_DIR accepts str with UPLOAD_KEEP_FILENAME (#335). A str upload directory used to fail on the first write to disk.
  • Decoded data is complete before callbacks run (#336, #355). Content-Transfer-Encoding decoders are finalized at the end of each part, and quoted-printable escapes split across writes decode correctly.
  • parse_options_header lowercases content types with parameters (#287). Multipart/Form-Data; boundary=abc now returns multipart/form-data, the same as headers without parameters.

⚡ Faster parsing

  • Faster opening boundary matching (#328). Complete boundaries are matched in one step.
  • Faster parser state lookups (#330). Parser states are module-level enum members, so their repr is now multipart.END instead of <MultipartState.END: 12>.
  • Faster querystring callback dispatch (#316).

🐍 Python support

  • Python 3.10 is no longer supported (#329). Python 3.11 is now the minimum.
  • Python 3.15 is supported (#350).

💜 Thank you

Thanks to @​Edneam, @​sungbin1015, @​carlok, and @​fjvbn2003 for contributing to this release.

Thanks to the individual sponsors who contributed $134.00 to support this work. If python-multipart is useful to you, consider sponsoring me on GitHub.

Full changelog: 0.0.32...0.0.33

Changelog

Sourced from python-multipart's changelog.

0.0.33 (2026-10-31)

  • Drop Python 3.10 support #329.
  • Add Python 3.15 support #350.
  • Add opt-in field-count and field-size limits for URL-encoded forms in FormParser #333.
  • Normalize the content type returned by parse_options_header when the header has parameters #287.
  • Finalize Content-Transfer-Encoding decoding before invoking field and file callbacks #336.
  • Keep only the incomplete escape when quoted-printable data is split across writes #355.
  • Handle nameless uploads when UPLOAD_KEEP_FILENAME or UPLOAD_KEEP_EXTENSIONS is set #343.
  • Accept a str UPLOAD_DIR when UPLOAD_KEEP_FILENAME is set #335.
  • Speed up parser state lookups #330.
  • Speed up opening boundary matching #328.
  • Speed up querystring callback dispatch #316.

0.0.32 (2026-06-04)

  • Speed up partial-boundary scanning for CR/LF-dense part data #300.

0.0.31 (2026-06-04)

  • Speed up multipart header parsing and callback dispatch #295.
  • Bound header field name size before validating #296.
  • Validate Content-Length is non-negative in parse_form #297.

0.0.30 (2026-05-31)

  • Parse application/x-www-form-urlencoded bodies per the WHATWG URL standard, treating only & as a field separator #290.
  • Ignore RFC 2231/5987 extended parameters (name*, filename*) in parse_options_header, keeping the plain parameter authoritative per RFC 7578 §4.2 #291.

0.0.29 (2026-05-17)

  • Handle malformed RFC 2231 continuations in parse_options_header #270.

0.0.28 (2026-05-10)

  • Speed up partial-boundary tail scan via bytes.find #281.
  • Cap multipart boundary length at 256 bytes #282.

0.0.27 (2026-04-27)

  • Add multipart header limits #267.
  • Pass parse offsets via constructors #268.

0.0.26 (2026-04-10)

  • Skip preamble before the first multipart boundary more efficiently #262.
  • Silently discard epilogue data after the closing multipart boundary #259.

0.0.25 (2026-04-10)

... (truncated)

Commits
  • 9217f26 Bump version to 0.0.33 (#357)
  • d0344c1 Keep only the incomplete escape when quoted-printable data is split (#355)
  • 44871df Handle nameless uploads when keeping the filename or extension (#343)
  • b21ea59 Add streaming field limits to FormParser (#333)
  • 48f9e21 Fix the In-Depth Example in the docs to return bytes (#338)
  • 12a2f8f Accept a str UPLOAD_DIR when UPLOAD_KEEP_FILENAME is set (#335)
  • 95f6376 Use the shared security policy (#353)
  • 8ec84ef Migrate documentation from MkDocs to Zensical (#352)
  • d7af81c Rewrite README for newcomers (#351)
  • b035d14 Add Python 3.15 classifier (#350)
  • Additional commits viewable in compare view

@dependabot
dependabot Bot requested a review from ARSH871-bot as a code owner November 9, 2026 09:25
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Nov 9, 2026
@dependabot
dependabot Bot force-pushed the dependabot/pip/runtime-f154f57835 branch from f201f11 to a62983f Compare November 16, 2026 09:24
@patelankeet2

Copy link
Copy Markdown
Collaborator

Not merging this one -- a real blocker, not a style objection.

requirements.txt's own comment on the pybatfish pin says:

Docker container should be on matching versions -- skew between them causes confusing failures. This pin matches image batfish/allinone reporting Batfish 2025.07.07.2423. If you pull a newer image, bump this to match.

This PR bumps the pin from 2025.7.7.2423 to 2026.9.17.3748 -- the client only. Dependabot cannot touch the Docker image, and mine is still reporting 2025.07.07.2423 (checked directly: pip show pybatfish on main is 2025.7.7.2423, matching the comment exactly). Merging this leaves the pinned client ahead of every developer's actual running image, which is precisely the configuration the comment warns against -- not a hypothetical, the project's own source names it.

CI's own check-runs for this PR are green on both Python versions, which is real evidence, not nothing -- but CI installs the new client against whatever Batfish image its own job runs, and I have not confirmed that job also updated the image rather than running the same skewed pair cleanly by luck. I did not pull a newer batfish/allinone image myself to test this properly, since that is an infrastructure change bigger than reviewing a dependency bump.

What this needs, not a quick merge: either (a) pull and pin a matching newer Batfish image and update the comment's version to match, with both tested together, or (b) tell dependabot to ignore major pybatfish bumps until that's done deliberately. Leaving this open for whoever owns the Docker image to decide -- flagging rather than guessing, same as this file's own comment asks.

Updates the requirements on [pybatfish](https://github.com/batfish/pybatfish), [pandas](https://github.com/pandas-dev/pandas), [ollama](https://github.com/ollama/ollama-python), [fastapi](https://github.com/fastapi/fastapi), [uvicorn](https://github.com/Kludex/uvicorn) and [python-multipart](https://github.com/Kludex/python-multipart) to permit the latest version.

Updates `pybatfish` from 2025.7.7.2423 to 2026.9.17.3748
- [Release notes](https://github.com/batfish/pybatfish/releases)
- [Commits](https://github.com/batfish/pybatfish/commits)

Updates `pandas` to 3.1.1
- [Release notes](https://github.com/pandas-dev/pandas/releases)
- [Commits](pandas-dev/pandas@v3.0.5...v3.1.1)

Updates `ollama` to 0.6.3
- [Release notes](https://github.com/ollama/ollama-python/releases)
- [Commits](ollama/ollama-python@v0.6.2...v0.6.3)

Updates `fastapi` to 0.163.1
- [Release notes](https://github.com/fastapi/fastapi/releases)
- [Commits](fastapi/fastapi@0.141.1...0.163.1)

Updates `uvicorn` to 0.54.0
- [Release notes](https://github.com/Kludex/uvicorn/releases)
- [Changelog](https://github.com/Kludex/uvicorn/blob/main/docs/release-notes.md)
- [Commits](Kludex/uvicorn@0.52.3...0.54.0)

Updates `python-multipart` to 0.0.33
- [Release notes](https://github.com/Kludex/python-multipart/releases)
- [Changelog](https://github.com/Kludex/python-multipart/blob/main/CHANGELOG.md)
- [Commits](Kludex/python-multipart@0.0.32...0.0.33)

---
updated-dependencies:
- dependency-name: fastapi
  dependency-version: 0.162.0
  dependency-type: direct:production
  dependency-group: runtime
- dependency-name: ollama
  dependency-version: 0.6.3
  dependency-type: direct:production
  dependency-group: runtime
- dependency-name: pandas
  dependency-version: 3.1.1
  dependency-type: direct:production
  dependency-group: runtime
- dependency-name: pybatfish
  dependency-version: 2026.9.17.3748
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: runtime
- dependency-name: python-multipart
  dependency-version: 0.0.33
  dependency-type: direct:production
  dependency-group: runtime
- dependency-name: uvicorn
  dependency-version: 0.54.0
  dependency-type: direct:production
  dependency-group: runtime
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/pip/runtime-f154f57835 branch from a62983f to ea4ecfb Compare November 19, 2026 02:06

@ARSH871-bot ARSH871-bot left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked ea4ecfb the way requirements.txt says a bump like this has to be checked, because CI can't. Commenting rather than approving: the bump works, but merged as it is, the file says something false.

It works against our container. An isolated venv with exactly this file (pybatfish 2026.9.17.3748, pandas 3.1.1, fastapi 0.165.0, uvicorn 0.54.0), the live suite with Batfish and Ollama running:

client  pybatfish 2026.09.17.3748
server  Batfish   2025.07.07.2423   (batfish/allinone, as running here)

live suite, main + this PR, new client   2503 passed, 13 skipped, 0 failed
same tests, old client (2025.7.7.2423)   2503 passed, 13 skipped

(The old-client run was on main plus #460, which adds five tests: 2508 there, so 2503 on the same tests.) CI-style on the merge: 2453 passed, 63 skipped. Ruff clean.

What is wrong is the comment above the pin, which this PR leaves as it was:

Pinned deliberately. The pybatfish client and the Batfish service in the Docker container should be on matching versions ... This pin matches image batfish/allinone reporting Batfish 2025.07.07.2423. If you pull a newer image, bump this to match.

After this merges, the pin no longer matches the image it names, and nothing says whether that was checked. Dependabot can't update a comment, so one of us has to, in one of two ways:

  1. Keep the old image, take the new client: change the comment to record what was measured above (client 2026.9.17 against server 2025.07.07, live suite identical), and push that to this branch.
  2. Move both: pull the matching batfish/allinone, re-run the live suite, and update the comment to name the new image. Everyone then needs to pull it too.

I'd take (1) now and (2) after the final submission, so nobody's working image changes this week. This is a team call, so I haven't pushed anything.

@ARSH871-bot

Copy link
Copy Markdown
Owner

Changing my recommendation above: I'd now hold this until after 27 November, then pull the matching batfish/allinone image and bump client and image together, because nothing we need depends on the new client and that avoids changing anyone's working setup in submission week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python Pull requests that update python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants