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

[beastoin]

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

[greptile-apps]

Greptile Summary

This is an auto-generated changelog update that adds a new release entry for v0.11.288 (dated 2026-04-11) to desktop/CHANGELOG.json and clears the unreleased array. The change is consistent with the existing format and version-numbering pattern used throughout the file.

Confidence Score: 5/5

Safe to merge — purely a data file update with no logic or runtime impact.

Single-file changelog update with no code changes; matches existing format and automated release workflow. No issues found.

No files require special attention.

Important Files Changed

Filename	Overview
desktop/CHANGELOG.json	Auto-generated changelog entry for v0.11.288 added; unreleased array cleared; format and versioning are consistent with existing entries.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR merged to main] --> B[desktop_auto_release.yml triggered]
    B --> C[Auto-increment version → v0.11.288]
    C --> D[Consolidate unreleased entries into new release]
    D --> E[Clear unreleased array]
    E --> F[Write desktop/CHANGELOG.json]
    F --> G[Push v0.11.288-macos tag]
    G --> H[Codemagic build triggered]
    H --> I[Sign, notarize, publish DMG]
    I --> J[Sparkle delivers update to users]

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