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

[beastoin]

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

[greptile-apps]

Greptile Summary

This PR adds a new release entry for v0.11.278 (dated 2026-04-10) to desktop/CHANGELOG.json, with a generic "Bug fixes and improvements" change description. The unreleased array was already empty in the base branch, so no entries were actually consolidated despite the PR description claiming otherwise.

Confidence Score: 5/5

Safe to merge — changelog-only update with no code changes.

Single JSON file change adding a versioned release entry; no logic, no code, no security surface. All findings are informational at best.

No files require special attention.

Important Files Changed

Filename	Overview
desktop/CHANGELOG.json	Adds v0.11.278 release entry; unreleased array remains empty (was already empty in base); version 0.11.277 is skipped in the sequence.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Auto-release script] --> B{Check unreleased entries}
    B --> |"unreleased: []"| C[Assign version 0.11.278]
    C --> D[Set date 2026-04-10]
    D --> E[Write 'Bug fixes and improvements']
    E --> F[Prepend to releases array]
    F --> G[Clear unreleased array]
    G --> H[Commit CHANGELOG.json with skip-ci]

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