Update CHANGELOG.json for v0.11.143 [skip ci]

[beastoin]

Auto-generated: consolidates unreleased entries into v0.11.143 and clears the unreleased array.

[greptile-apps]

Greptile Summary

This PR auto-generates a new v0.11.143 entry in desktop/CHANGELOG.json, intended to consolidate unreleased changes and clear the unreleased array. However, the unreleased array was already empty prior to this change, so the new release entry carries only the generic fallback message "Bug fixes and improvements" rather than real release notes.

Key observations:

• The unreleased array was empty before this PR, so no entries were actually consolidated — the changelog entry for v0.11.143 contains no meaningful content.
• Multiple consecutive versions (0.11.138, 0.11.139, 0.11.142, 0.11.143) all share the same generic "Bug fixes and improvements" placeholder, which reduces the utility of the changelog for users and contributors.
• Version 0.11.140 appears to be absent from the releases list (the sequence jumps from 0.11.139 to 0.11.141), which may indicate a skipped or untracked version bump.

Confidence Score: 4/5

• Safe to merge — only a changelog JSON update with no functional code changes.
• The change is limited to a documentation/metadata file and introduces no runtime risk. The main concern is that the new release entry was generated from an empty unreleased array, producing a meaningless placeholder rather than real release notes, but this does not block merging.
• desktop/CHANGELOG.json — the v0.11.143 entry should ideally reflect actual changes rather than a generic fallback.

Important Files Changed

Filename	Overview
desktop/CHANGELOG.json	Adds a new v0.11.143 release entry with a generic "Bug fixes and improvements" message; the unreleased array was already empty before this change, so no actual entries were consolidated.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Auto-generation script triggered] --> B{Are there entries\nin 'unreleased' array?}
    B -- Yes --> C[Consolidate entries\ninto new version]
    B -- No --> D[Use generic fallback:\n'Bug fixes and improvements']
    C --> E[Create v0.11.143 entry\nwith real changes]
    D --> F[Create v0.11.143 entry\nwith placeholder text]
    E --> G[Clear 'unreleased' array]
    F --> G
    G --> H[Commit CHANGELOG.json]
    style D fill:#f9c74f,color:#333
    style F fill:#f9c74f,color:#333

Loading

_{Last reviewed commit: "chore: consolidate c..."}

[greptile-apps]

Changelog entry created from empty unreleased array

The PR description states this auto-generation "consolidates unreleased entries into v0.11.143 and clears the unreleased array." However, looking at the diff, the unreleased array was already empty in the base branch before this change — there were no entries to consolidate. As a result, the changes field falls back to the generic placeholder "Bug fixes and improvements" rather than containing real release notes.

If v0.11.143 genuinely includes meaningful changes, those should be captured in the unreleased array before running the consolidation script, or the changes should be listed explicitly here. If this version was created with no tracked changes, the entry itself may be misleading.