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

[beastoin]

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

[greptile-apps]

Greptile Summary

This PR auto-generates a changelog consolidation: it moves the single unreleased entry ("Fixed floating bar close button requiring multiple clicks by enlarging the hit area") into a new v0.11.290 release dated 2026-04-11 and clears the unreleased array. No code changes are included.

Confidence Score: 5/5

Safe to merge — purely a changelog data file update with no logic changes.

Only one file changed (desktop/CHANGELOG.json), the version number (0.11.290) correctly follows the prior highest release (0.11.287), the date matches today, and the unreleased entry accurately reflects the preceding close-button fix commit. No code or configuration changes are present.

No files require special attention.

Important Files Changed

Filename	Overview
desktop/CHANGELOG.json	Adds v0.11.290 release entry with one change and clears the unreleased array; straightforward changelog consolidation with correct date and sequential version number.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["unreleased[]\n• Fixed floating bar close button..."] -->|consolidate| B["releases[0]\nv0.11.290 · 2026-04-11"]
    B --> C["unreleased[] cleared (empty)"]

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! 💜