Update CHANGELOG.json for v0.11.97 [skip ci]#5609
Conversation
Greptile SummaryThis PR is an auto-generated changelog bump that adds a
Confidence Score: 5/5
Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Auto-generated Script Runs] --> B{Check unreleased array}
B -->|Empty| C[No entries to consolidate]
B -->|Has entries| D[Collect unreleased changes]
C --> E[Create new version entry\nv0.11.97 with generic message]
D --> E
E --> F[Prepend to releases array]
F --> G[Clear unreleased array]
G --> H[Commit CHANGELOG.json\nwith skip ci]
Last reviewed commit: d449aaf |
| "unreleased": [], | ||
| "releases": [ | ||
| { | ||
| "version": "0.11.97", | ||
| "date": "2026-03-13", | ||
| "changes": [ | ||
| "Bug fixes and improvements" | ||
| ] |
There was a problem hiding this comment.
Empty unreleased array — nothing was actually consolidated
The PR description states this "consolidates unreleased entries into v0.11.97 and clears the unreleased array," but the diff shows the unreleased array was already [] before this commit. No entries were moved; a new version was minted with a generic placeholder message despite having no accumulated changelog entries.
This pattern repeats across many recent releases (v0.11.93–v0.11.97 all dated 2026-03-13, all with "Bug fixes and improvements"), suggesting the auto-generation script cuts a new version unconditionally, even when there is nothing to release. Consider either:
- Gating the script so it only creates a new release when
unreleasedis non-empty, or - Ensuring real change descriptions are written to
unreleasedbefore the consolidation script runs.
Auto-generated: consolidates unreleased entries into v0.11.97 and clears the unreleased array.