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

[beastoin]

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

[greptile-apps]

Greptile Summary

This auto-generated PR consolidates the unreleased array in desktop/CHANGELOG.json into a new versioned release entry v0.11.292, dated 2026-04-11. The single change entry — "Fixed floating bar close button requiring multiple clicks by enlarging the hit area" — is properly moved from unreleased into the releases array, and unreleased is cleared.

Confidence Score: 5/5

This PR is safe to merge — it is a trivial, auto-generated changelog update with no logic changes.

Only one JSON file is touched; the change is purely additive (new versioned release entry) and non-breaking. No code is modified, no logic is affected, and the format follows the established schema exactly.

No files require special attention.

Important Files Changed

Filename	Overview
desktop/CHANGELOG.json	Auto-generated changelog consolidation: moves one unreleased entry into v0.11.292, clears the unreleased array. JSON is valid and follows existing structure.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["unreleased array\n['Fixed floating bar close button...']"] -->|auto-consolidation script| B["releases[0]\nversion: 0.11.292\ndate: 2026-04-11\nchanges: ['Fixed floating bar...']"]
    A -->|cleared| C["unreleased: []"]

Loading

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

[beastoin]

Closing: orphaned changelog PR — conflicts with main. See #6561 for fix. The release tag already has the correct changelog data.

[github-actions]

Hey @beastoin 👋

Thank you so much for taking the time to contribute to Omi! We truly appreciate you putting in the effort to submit this pull request.

After careful review, we've decided not to merge this particular PR. Please don't take this personally — we genuinely try to merge as many contributions as possible, but sometimes we have to make tough calls based on:

• Project standards — Ensuring consistency across the codebase
• User needs — Making sure changes align with what our users need
• Code best practices — Maintaining code quality and maintainability
• Project direction — Keeping aligned with our roadmap and vision

Your contribution is still valuable to us, and we'd love to see you contribute again in the future! If you'd like feedback on how to improve this PR or want to discuss alternative approaches, please don't hesitate to reach out.

Thank you for being part of the Omi community! 💜