chore(deps): bump gunicorn from 26.0.0 to 26.2.0

[dependabot]

Bumps gunicorn from 26.0.0 to 26.2.0.

Release notes

Sourced from gunicorn's releases.

gunicorn 26.2.0

Cleartext HTTP/2 lands, and an HTTP/2 security fix.

Cleartext HTTP/2 (h2c)

http2_cleartext accepts prior-knowledge, upgrade, both or off (the default). Prior knowledge serves a connection that opens with the HTTP/2 preface; upgrade honours an HTTP/1.1 Upgrade: h2c request. Both work on the gthread, gevent and asgi workers.

This is for deployments where TLS is terminated by a proxy that speaks HTTP/2 upstream, so the hop into gunicorn no longer drops to HTTP/1.1. Only peers in forwarded_allow_ips are considered; everyone else is served HTTP/1.x exactly as if the setting were off. Each mechanism is enabled separately, so turning one on does not turn the other on.

Do not expose a cleartext HTTP/2 port to the internet.

Security

HTTP2Request built its headers straight from the stream, so nothing the HTTP/1 path enforces applied over HTTP/2: the underscore and header_map policy, duplicate Host and Content-Type, control characters in values, and the forwarded_allow_ips trust gate. An untrusted client could set SCRIPT_NAME and forge HTTP_* entries in the WSGI environ, and decide wsgi.url_scheme through :scheme. Both request classes now share one policy mixin, and the scheme comes from the transport.

If you serve HTTP/2, this is the reason to upgrade.

Other HTTP/2 fixes

WSGI responses were buffered whole before anything was sent; they stream now. HEAD, 204 and 304 no longer carry a body. Events read while blocked on a flow-control window were discarded, losing requests and body data outright. sendfile() is refused on HTTP/2 responses rather than bypassing framing.

Request bodies dropped on Upgrade requests

On the ASGI worker with the fast parser, any request carrying an Upgrade header reached the application with an empty body, whatever the header's value and with HTTP/2 switched off entirely. Fixed in gunicorn_h1c 0.6.9, which the fast extra now requires.

Full changelog: https://gunicorn.org/news/

gunicorn 26.1.0

New Features

• Glob patterns in reload_extra_files: entries containing *, ? or [

... (truncated)

Commits

• 36f2a3c gunicorn 26.2.0
• cbba350 test: cover the h2c edge paths that had none
• 9885411 Merge pull request #3703 from cormier/fix-inconsistency-in-control-socket-docs
• 86f0919 Merge pull request #3704 from methane/doc-wsgi-h1c
• 5853551 Merge pull request #3712 from Rotzbua/patch-1
• 7bce87e Merge pull request #3700 from benoitc/fix/sponsor-logo-path
• 972dfb0 Merge pull request #3690 from melbinjp/docs/contributing-settings-path
• 7b3f16b Merge pull request #3711 from benoitc/docs/http2-changelog
• 5bf237c http2: require gunicorn_h1c 0.6.9 and drop the upgrade body workaround
• 7cf0338 test: skip the fast-parser cases when gunicorn_h1c is absent
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[rtibblesbot]

🟡 Waiting for changes

Last updated: 2026-09-01 00:51 UTC

[rtibblesbot]

PR #6121 — gunicorn 26.0.0 → 26.2.0, minor bump of a production dependency (requirements.in; run by Makefile:17 altprodserver and .github/workflows/deploytest.yml:208). CI passing, including the Browser smoke test, which starts gunicorn at the new version.

Breaking changes: none for HTTP/1.1. No settings removed or renamed; Studio uses gthread over HTTP/1.1 behind nginx with CLI flags only.

Security: HTTP/2-only. HTTP2Request bypassed the HTTP/1 header policy, letting an untrusted client set SCRIPT_NAME, forge HTTP_* environ entries, and pick wsgi.url_scheme via :scheme. Not reachable here — h2 is not in requirements.txt, so the http2 extra is not installed and http2_cleartext defaults to off. 26.1.0 also raised floors on tornado/h2/setuptools/pymdown-extensions, all in extras Studio does not install.

Peer/dependency changes: packaging moved from unconditional to extra == "gevent" / extra == "testing" — that is the requirements.txt:193 via-line removal. packaging==26.2 stays pinned via kombu, django-js-reverse and google-cloud-error-reporting, so nothing is uninstalled.

Behavioral changes worth knowing about:

• suggestion: 26.1.0 tightened request parsing — duplicate Host/Content-Type now raise InvalidHeader (#3366), and a chunked body truncated after the last chunk line raises ChunkMissingTerminator instead of being treated as complete (#3382). Low risk behind nginx, but malformed uploads go from silently accepted to 400. Worth watching if anything posts chunked bodies straight to gunicorn.
• Fixes that do apply: a dirty arbiter no longer returns a stale response to the wrong request after a worker timeout (#3626), and reparented non-worker children under PID 1 no longer log as failed workers or halt the server with exit 3/4 (#3220) — both relevant to the containerized deploy. SIGHUP now also reloads logger config.
• nitpick: requirements.txt:101 and :140 drop the [grpc] extras marker from google-api-core and googleapis-common-protos — unrelated to gunicorn, just a rendering difference from dependabot's uv. Functional no-op (grpcio, grpcio-status, protobuf all still pinned), but if a local uv pip compile requirements.in -o requirements.txt re-adds [grpc], every future dependabot PR will keep flipping these two lines.

---

@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly

How was this generated?

Ran a dependency-update review pipeline over the version bump:

• Classified the bump by semver (patch / minor / major) and dependency type (production vs. development)
• Extracted the changelog and release notes across the version range
• Assessed compatibility with this project's usage and whether any code changes are required
• Treated CI as the primary safety net
• Scaled the review depth to the update's risk
• Chose the verdict from semver risk, changelog findings, and CI status