chore(release): 0.60.6

[client-software-ci]

0.60.6 (2026-08-25)

[github-actions]

The 0.60.6 entry is added with no content and no blank line after the heading, so the top of the file now reads ## 0.60.6 (2026-08-25) immediately followed by ## 0.60.5 (2026-08-24) and then 0.60.5's ### Features section. Two things differ from every other entry in this file and from the generator template (.semantic_release/CHANGELOG.md.j2 emits the version heading followed by a blank line).

1. No blank line after the heading. Any tooling that extracts notes for the latest release by slicing between the first two level-2 headings gets an empty string, and a reader skimming the file sees 0.60.6 directly abutting 0.60.5's ### Features, which is easy to misread as belonging to 0.60.6.

2. No sections at all. The three commits between 0.60.5 and this release are test: (#1340), docs: (#1337), and chore(deps): (#1335) — none map to a ### Features or ### Bug Fixes heading under the template, which explains the empty body. But #1335 raises the openjd-model floor from >=0.11.2 to >=0.11.3, which is user-visible at install time: it can force a transitive upgrade for anyone pinning openjd-model, notably in the embedded-Python environments this library targets. Prior releases did document comparable dependency-floor changes as user-facing entries — 0.60.4's Constrained the MCP dependency to v1... and 0.60.3's The minimum click dependency has been raised to >= 8.3.3....

Worth confirming this is the intended shape of the release rather than a partially-generated entry, since publishing a version whose only changelog content is a bare heading gives consumers nothing to act on.

[karthikbekalp]

If we don't have any customer useful features, then I think its ok to just skip. :)

[karthikbekalp]

If we don't have any customer useful features, then I think its ok to just skip. :)

[karthikbekalp]

If we don't have any customer useful features, then I think its ok to just skip. :)

[leon-li-inspire]

Closing: 0.60.6 has no release-worthy changes. The only commits since 0.60.5 are docs (#1337), a test fix (#1340), and a dependency-requirement bump (#1335) — all non-feat/fix, so the changelog is empty. Not cutting a maintenance-only release. Deleting the bump/0.60.6 branch.