Skip to content

chore(release): 0.60.6 #1345

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.60.6 #1345

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
1 change: 1 addition & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
## 0.60.6 (2026-08-28)

@github-actions github-actions Bot Aug 28, 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 0.60.6 entry is empty: the header is immediately followed by the 0.60.5 header with no blank line and no ### Features / ### Bug Fixes section. Every other release header in this file is followed by a blank line and at least one section, and CHANGELOG_GUIDELINES.md states each release must follow the standard section order.

This looks like a side effect of the three commits since 0.60.5 (chore(deps) bumping openjd-model in requirements-testing.txt / requirements-ui-testing.txt, plus a test: and a docs: commit). Since chore is listed in [tool.semantic_release.commit_parser_options].patch_tags, the test-only dependency bump triggered a patch version bump but produced no user-facing entry — so 0.60.6 would publish with no changes to the distributed package and an empty changelog section.

Two things worth deciding before merging:

  1. Either give the entry a one-line body (e.g. a ### Bug Fixes / maintenance note) or drop the bare header, so the file stays parseable and consistent.
  2. If test-requirement-only chore(deps) bumps should not cut releases, consider removing chore from patch_tags (or scoping it) so dependabot updates to requirements-*testing.txt do not produce empty releases.

## 0.60.5 (2026-08-24)

### Features
Expand Down
Loading