chore(release): 0.11.0

[client-software-ci]

0.11.0 (2026-08-18)

Features

• shorten the session working directory name for Windows MAX_PATH (feat!: shorten the session working directory name for Windows MAX_PATH #348) (3252e69)
• shorten the session working directory name for Windows MAX_PATH (3252e69)

[github-actions]

The release this entry documents is a breaking one, but the generated notes contain no ### BREAKING CHANGES section.

3252e69 is feat!: and carries a BREAKING CHANGE: footer (on-disk session working directory is no longer prefixed with the session id; embedded-files subdir renamed embedded_files<rand> → ef<rand>, with a named downstream consumer in deadline-cloud-worker-agent). semantic-release clearly did see it — feat is only in patch_tags and minor_tags is empty, so the 0.10.14 → 0.11.0 minor bump can only come from the breaking flag with major_on_zero = false. Yet the rendered section is missing, so the one thing consumers grep the changelog for is absent for the only release that needs it.

The likely cause is .semantic_release/CHANGELOG.md.j2:4:

{% if "breaking" in release["elements"] %}

release.elements is keyed by parsed commit type (features, bug fixes, …); "breaking" was a v8-era key. Under python-semantic-release == 10.6.* (requirements-release.txt) breaking descriptions come off the commits themselves (commit.breaking_descriptions), so this branch can never be true and the block is dead. That matches history: every prior ### BREAKING CHANGES block in this file (0.10.0 and earlier) predates the 10.x upgrade.

Suggested handling: fix the template to collect breaking descriptions from the release's commits, then regenerate — or, if regenerating is awkward on a release commit, hand-add the ### BREAKING CHANGES section here so 0.11.0 isn't published without it. Either way the template bug will silently swallow the next breaking release too.

Also cosmetic, same block: the feature is listed twice (lines 5-6) because the squash-merge body repeats the feat!: subject as a bullet, and both get parsed as commits. Worth de-duplicating while editing.