chore(release): bump desktop version to v2026.5.19#742
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe desktop-electron package version in ChangesVersion Bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
2026.5.19.Why
v2026.5.18shipped before the latest terminal input, Kimi reasoning, OfficeCLI skills, model picker, event-stream noise, diagnostics, CI, and Windows advisory fixes. This PR prepares the next stable release from currentdevwithout including PR #735.Related Issue
No dedicated release issue. This release includes the merged work currently on
devafterv2026.5.18, including #707, #708, #710, #715, #718, #722, #723, #727, #729, #730, #731, #732, and #739.Human Review Status
Pending. A human should make the final merge decision after reviewing the final diff and verification evidence.
Review Focus
Please check that the version bump is limited to the desktop package and that this release branch does not include PR #735.
Risk Notes
Low product risk. The only file change is the desktop package version. Release risk is the normal desktop publishing path: macOS notarization, Windows build, release assets, updater metadata, and post-release verification still need to pass after merge.
How To Verify
Screenshots or Recordings
Not required. No visible UI change in this PR.
Checklist
bug,enhancement,task, ordocumentation), at least one primary routing label (app,ui,platform,harness, orci), and exactly one priority label (P0toP3), or I requested maintainer labelingdev, and my PR title and commit messages use Conventional Commits in EnglishSummary by CodeRabbit