Originally created by: kristofferR
The v1.0 release shipped via [#2] (feat/v1.0 → main), which was merged without any CodeRabbit or Codex review. The follow-up review PR (#4, based on pre-v1.0) didn't help: even though its GitHub diff included the v1.0 code, CodeRabbit anchors its review to main, not to the PR base — so it skipped every commit already merged into main (all the v1.0 feature commits) and only looked at the post-merge test/theme commits.
This PR fixes that by replaying the v1.0 + post-1.0 changes as fresh commits off pre-v1.0, with no merge commit in the lineage. None of these SHAs are on main, so the bots review the entire v1.0 diff from scratch.
Linear replay of the release (identical tree to the current fix/v1.0-review head, minus local dev scaffolding):
wants_tray() so the tray tests exercise real codeNot included: the tauri-mcp dev-tooling commit (local scaffolding, not release code).
Review-only — supersedes [#4] for review purposes. Ref [#2], Ref [#4].
Release artifacts now use stable, predictable names across platforms.
Bug Fixes
Originally posted by: chatgpt-codex-connector[bot]
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.
Originally posted by: coderabbitai[bot]
✨ Finishing Touches
🧪 Generate unit tests (beta)
- [ ] Create PR with unit tests - [ ] Commit unit tests in branch `review/v1.0-clean`Comment
@coderabbitai helpto get the list of available commands.Originally posted by: kristofferR
Fixes from this review were applied directly to
fix/v1.0-review(commit ee49f3f) instead of merging this branch: notarization fail-fast, IPTVChecker-style README auto-update at release (keeping versioned filenames), and the macOS theme-rebuild gating + close-handler reattach (single-flight was already there). Closing in favor of that branch.Ticket changed by: kristofferR