S3 and proxy fixes. On the S3 side, list_objects now checks request params for invalid UTF-8 bytes, and some noisy s3api logging was cleaned up. Encryption became more tolerant of errors while decrypting listings, tempurl/staticweb listings with ?inline were fixed to work as intended, and the inline account-update timeout stopped pulling logging into the hot path.

Object server and updater. The object server uses conn_timeout in more places, and object-updater settings docs were clarified.

Tooling. The CORS job is voting again, gettext was dropped from bindep, and a stale note about old pip behavior was removed from the docs.

Crypto and eventlet. A crypto listings bug is fixed for the case where the middleware pipeline is misconfigured, so container listings behave sanely instead of surfacing encrypted metadata. On the runtime side, Swift gains a flag to disable eventlet entirely, and separately quiets the eventlet deprecation warnings that have been cluttering logs and test output.

Release plumbing. The bulk of the week is release mechanics: AUTHORS and CHANGELOG for 2.38.0, plus CHANGELOG entries for the 2.37.2, 2.36.2 and 2.35.3 stable releases, forward-ported onto master so history stays linear.

CI. Rolling-upgrade jobs are repaired across three branches, the swift-multinode-rolling-upgrade-dalmatian job gets a one-line fix in the same three places, and a failing CORS job is made non-voting on four branches while it's investigated.

Gatekeeper hardening. The gatekeeper middleware now blocks X-Container-Host and the other internal update headers from arriving via client requests, with the same fix landed on master and backported across three stable branches. On the edge protocol side, s3api now asks the client to close the connection on RequestTimeout rather than leaving it in an ambiguous state.

Stability and internals. Metadata servers now explicitly close their DB connections, the largest single patch of the week at ~475 lines touched. The Timestamp offset handling was simplified, with validation cleaned up and zero now accepted as a valid offset. swift-ring-builder write_ring gained a --dev-id-bytes knob, and a flaky test_DELETE_container_updates timestamp collision was fixed.

Test coverage. Dispersion reports gained a ~300-line test suite filling out previously thin coverage.

S3 API surface. Beyond the hardening, s3api picked up support for the x-amz-server-side-encryption response header (990318), learned to handle empty Quiet elements in S3 multi-delete requests, and added publicAccessBlock to the not-implemented list so clients get a clean rejection rather than confusing behavior.

Diagnostics. ssync_receiver log lines are now uniformly annotated with the object path, and the relinker logs unexpected worker failures instead of swallowing them — both targeted at making field debugging less archaeological.

Tooling and CI. A handful of stable-only fixes kept older branches green, including pinning to older OpenStack requirements and pinning tempest; CHANGELOG entries for stable releases were forward-ported to master, and a .mailmap entry was refreshed.

Timestamps and versioning. Swift's Timestamp type gained richer offset support through __invert__, with a follow-up refining the offset semantics. Object versioning was reworked to use x-backend-timestamp as the source version, replacing the previous approach for picking which version to restore.

s3api aws-chunked. Truncated aws-chunked uploads are now rejected with an explicit error rather than being silently accepted, landing alongside functional tests that exercise the truncation path and a second round of functional coverage for additional cases.

CI and docs. A new swift-multinode-rolling-upgrade-gazpacho job joins the rolling-upgrade matrix and the dalmatian variant got a small fix; the py310 unit-test job is pinned to stable/2026.1 constraints. The SAIO setup guide was trimmed of outdated instructions, and a flaky sharder test was made more robust.