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

[beastoin]

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

[greptile-apps]

Greptile Summary

This is a single-file, auto-generated changelog update that promotes one pending entry from unreleased into a new v0.11.223 release record and clears the unreleased array. The change is mechanical and low-risk.

• The new release entry (v0.11.223, dated 2026-04-04) describes "Fixed speaker diarization in Take Note by migrating live transcription to production backend" — which is word-for-word identical to the v0.11.221 entry two positions earlier. This is worth verifying: if the fix was re-applied because v0.11.221 was incomplete, the entry should distinguish the two attempts for release-note clarity.
• Version number 0.11.216 is absent from the history (sequence jumps 0.11.217 → 0.11.215), which is consistent with build numbers that can be skipped in automated pipelines, so this is not concerning on its own.
• JSON structure is valid, the date matches today's date, and the unreleased array is correctly emptied.

Confidence Score: 4/5

Safe to merge — this is a mechanical, auto-generated changelog update with no functional code changes.

The PR touches only desktop/CHANGELOG.json with a valid JSON structure. The only notable concern is that the changelog description for v0.11.223 is identical to v0.11.221, which is worth a clarifying look but does not block merging.

desktop/CHANGELOG.json — verify that the duplicate change description between v0.11.223 and v0.11.221 is intentional.

Important Files Changed

Filename	Overview
desktop/CHANGELOG.json	Auto-generated changelog update consolidating unreleased entries into v0.11.223 and clearing the unreleased array; the new release's change description is identical to v0.11.221's entry, which may indicate the same fix was applied twice

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["unreleased array\n['Fixed speaker diarization...']"] -->|"Auto-release script"| B["New release entry\nv0.11.223 / 2026-04-04"]
    B --> C["releases[] array\n(prepended at index 0)"]
    A -->|"Cleared"| D["unreleased: []"]
    C --> E["v0.11.223 ← new\nv0.11.222\nv0.11.221 ← same description!\nv0.11.220\n..."]

Loading

_{Reviews (1): Last reviewed commit: "chore: consolidate changelog for v0.11.2..." | Re-trigger Greptile}

[greptile-apps]

Duplicate changelog entry across two releases

The change description for v0.11.223 is word-for-word identical to the one already published in v0.11.221 (line 21):

"Fixed speaker diarization in Take Note by migrating live transcription to production backend"

If this truly is a second attempt to land the same fix (e.g., v0.11.221 didn't fully resolve the issue), the entry for v0.11.223 should describe what is different from the previous attempt — otherwise users and release notes readers have no way to distinguish the two versions. If it is the same code artifact being re-released, the description should note that (e.g., "Re-released fix for speaker diarization…").