Skip to content

chore(release): 0.11.0 #352

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
client-software-ci wants to merge 1 commit into from
Closed

chore(release): 0.11.0 #352

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,12 @@
## 0.11.0 (2026-08-18)


### Features

@github-actions github-actions Bot Aug 18, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

* shorten the session working directory name for Windows MAX_PATH (#348) ([`3252e69`](https://github.com/OpenJobDescription/openjd-sessions-for-python/commit/3252e693eec2cb31a0546f12e0e39f5778d9eb9d))
* shorten the session working directory name for Windows MAX_PATH ([`3252e69`](https://github.com/OpenJobDescription/openjd-sessions-for-python/commit/3252e693eec2cb31a0546f12e0e39f5778d9eb9d))



## 0.10.14 (2026-08-11)

### Features
Expand Down
Loading