Temporal Python SDK Caps Eager-Activity Reservations Per Task

Temporal shipped Python SDK version 1.31.0 on July 29, adding a cap on eager activity slot reservations per workflow task, per the release notes.

That's a capacity knob for teams running many concurrent agent workflows on the same worker. Temporal is increasingly the durable-execution layer underneath long-running agent systems, the release notes say.

The same release adds TLSConfig.verification_server_name, letting a Python worker verify a certificate against a fixed name. That check happens without altering TLS SNI or the HTTP/2 authority, the setup SNI-inspecting egress proxies require, per the release notes.

The release also adds an experimental patch_activation_callback, for rolling-deploy patch semantics. It's aimed at deployments where old and new workflow code have to coexist mid-rollout, according to the changelog.

Not dramatic on their own. Together they read as upkeep for Temporal at agent scale: tighter control over shared worker capacity, plus a TLS path for locked-down, proxy-heavy networks.