chore(release): 0.31.0

[client-software-ci]

0.31.0 (2026-08-10)

Features

• Rust session runtime adapter: sessions can run on the OpenJD v1 Rust runtime as an alternative to the Python runtime. Select it by setting session_runtime in worker.toml to python, rust, or service-selected. (feat: add RustSessionRuntime adapter for OpenJD v1 sessions #1002)
• With service-selected, the session runtime (Python or Rust) is chosen from a runtimeHint provided by the service, defaulting to Python when no hint is given. (feat: add select_runtime() to resolve session runtime mode #1009, feat: consume runtimeHint from UpdateWorkerSchedule responses #1016)
• Runtime selection and failure telemetry events added. To opt out, set opt_out = true under [telemetry] in worker.toml, pass --telemetry-opt-out to the installer, or set the DEADLINE_CLOUD_TELEMETRY_OPT_OUT=true environment variable. (feat: emit runtime selection and failure telemetry events #1021)

Bug Fixes

• Wrap-environment jobs failed on both the Python and Rust runtimes because step_name wasn't forwarded, leaving RFC 0008's WrappedStep.Name unresolved; both runtime paths now forward it. (fix: thread step_name to run_task for wrap-action support #1039, fix: forward step_name on the Rust runtime and add e2e test-rust script #1040)
• Rust runtime panics no longer silently kill the session thread; they are now reported as a failed session with proper cleanup and telemetry. (fix: convert runtime crashes at the adapter boundary and emit failure telemetry #1026)
• Transient network errors (connection closed, connect/read timeout, endpoint connection) are now retried with exponential backoff instead of terminating the agent. (fix: retry transient network errors in UpdateWorkerSchedule #1013)
• Credentials expiring mid-call during hibernate/sleep no longer cause an unrecoverable exit; the agent now detects the time jump and retries with bootstrap credentials. (fix(credentials): Retry with bootstrap creds on hibernate/sleep expiry #1014)

[github-actions]

This adds a second ## 0.31.0 section, so the changelog now contains two headings for the same version (0.31.0 (2026-08-11) here and 0.31.0 (2026-08-10) at line 16) with overlapping content:

• Rust session runtime adapter (feat: add RustSessionRuntime adapter for OpenJD v1 sessions #1002) — listed in both
• Runtime selection/failure telemetry (feat: emit runtime selection and failure telemetry events #1021) — listed in both
• step_name wrap-env fixes (fix: thread step_name to run_task for wrap-action support #1039, fix: forward step_name on the Rust runtime and add e2e test-rust script #1040) — listed in both
• Rust panic handling (fix: convert runtime crashes at the adapter boundary and emit failure telemetry #1026) — listed in both
• Transient network retries and hibernate/sleep credential expiry — listed in both, but with different PR attributions (fix(test): resolve worker agent PID via systemd in cap_kill e2e test #1033 here vs. fix: retry transient network errors in UpdateWorkerSchedule #1013/fix(credentials): Retry with bootstrap creds on hibernate/sleep expiry #1014 at lines 26-27)

Since tag_format = "{version}" in pyproject.toml, there can only be one 0.31.0 tag, so one of these two sections describes a release that will never exist under that number. The 2026-08-10 section (from 9c4ac8a) was hand-curated to dedupe and link PRs; this regenerated section appears to have been stacked on top of it rather than replacing it.

Suggest either folding the genuinely new entries into the existing 0.31.0 section, or bumping this one to the next version if 0.31.0 has already been tagged/published.

[github-actions]

These two entries attribute the network-retry and credential-expiry fixes to #1033, but #1033 is the e2e test commit 2457b71 fix(test): resolve worker agent PID via systemd in cap_kill e2e test (#1033). The actual fixes are af02f3f fix: retry transient network errors in UpdateWorkerSchedule and 528cd41 fix(credentials): Retry with bootstrap creds on hibernate/sleep expiry, neither of which carries a PR number in its commit subject — which is likely why the generator fell back to the nearest numbered commit.

The existing 0.31.0 section (lines 26-27) attributes the same two fixes to #1013 and #1014. At most one attribution can be right; worth confirming the correct PR numbers before publishing.