Skip to content
Merged
Changes from 1 commit
Commits
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
15 changes: 15 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,18 @@
## 0.11.0 (2026-08-19)


### Features

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Missing BREAKING CHANGES section for 0.11.0.

3252e69 is a feat!: commit with an explicit BREAKING CHANGE: footer -- the on-disk session working directory name is no longer prefixed with the session id, and the embedded-files subdir is now ef<random> instead of embedded_files<random> (the footer even names a known downstream consumer). The changelog template renders a breaking-changes block when release["elements"] contains breaking, and prior releases (0.10.0, 0.8.0, 0.7.0, ...) have one, but this entry lists the change only under Features.

So the one thing a consumer most needs to see when bumping to 0.11.0 is absent from the release notes. Suggest adding the breaking-change text manually before merge, summarizing the footer: the working directory name no longer carries the session id and the embedded files subdirectory is renamed, while Session.working_directory, Session.files_directory, and OPENJD_SESSION_WORKING_DIR are unchanged -- anything that pattern-matches the directory name must be updated.

Related: the version was bumped as a minor (0.11.0) rather than a major, which is expected given major_on_zero = false in pyproject.toml -- which makes this changelog text the only signal consumers get about the break.

* 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))

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Duplicate entry: lines 5 and 6 are the same commit (3252e69) listed twice — once with the PR number and once without.

This looks like python-semantic-release 10.x's parse_squash_commits (default on) splitting the squash-merge commit body. That body literally contains a bullet * feat!: shorten the session working directory name for Windows MAX_PATH, so the merge summary and the embedded bullet each get parsed as a feat, both resolving to the same hash.

Worth either setting parse_squash_commits = false under [tool.semantic_release.commit_parser_options] in pyproject.toml, or hand-removing the duplicate line before merging — otherwise every future squash-merged PR whose body repeats its conventional-commit subject will double up in the changelog.


### Bug Fixes
* raise openjd-model floor to >= 0.11.4 ([`ea0ea7f`](https://github.com/OpenJobDescription/openjd-sessions-for-python/commit/ea0ea7ffe885fd9c6ad7fd18d9ed04d8fe1ebf38))
* do not cache failed command lookups ([`3574ced`](https://github.com/OpenJobDescription/openjd-sessions-for-python/commit/3574ced5dc0c042fd74a12557f4f068ea9823a0b))
* address automated review findings on the trusted-path resolver ([`3744653`](https://github.com/OpenJobDescription/openjd-sessions-for-python/commit/37446538e6f6ba3ec2b5d9d77f1ea1a80b86c1bd))
* resolve system commands from trusted dirs, not PATH ([`419b434`](https://github.com/OpenJobDescription/openjd-sessions-for-python/commit/419b434cc2a0f01484f2d3c0c67adea0eab60a08))
* use absolute paths for system commands to prevent PATH injection ([`d3b978f`](https://github.com/OpenJobDescription/openjd-sessions-for-python/commit/d3b978f5deb4557e8f49b5d5cd4e9ce30e6d04c5))


## 0.10.14 (2026-08-11)

### Features
Expand Down
Loading