chore(release): bump desktop version to v2026.5.25

[Astro-Han]

Summary

Bump the desktop Electron package version to v2026.5.25 for the next PawWork release. There is no related issue because this is the release train version bump.

Why

The v2026.5.25 release needs to include the latest merged PRs on dev, especially #874, #878, #880, #881, and #883.

Related Issue

None. Release version bump only.

Human Review Status

Not required: automated release version bump only.

Review Focus

Confirm the version is updated only in the desktop Electron package metadata and lockfile workspace entry.

Risk Notes

Low risk. This PR does not change runtime behavior, dependencies, generated files, UI, docs, or permissions. Platform impact is limited to the release package version metadata used by desktop builds.

How To Verify

Version check: packages/desktop-electron/package.json reports 2026.5.25.
Typecheck: bun --cwd packages/app typecheck && bun --cwd packages/desktop-electron typecheck passed.
Focused UI tests: bun --cwd packages/ui test src/components/message-part/grouping.test.ts src/components/session-turn-trow-block.reducer.test.ts src/components/message-part-registry.test.ts passed, 34 tests.
Computer Use manual E2E: Electron dev app started with version 2026.5.25; created a new session; ran an actual Execute command tool call; verified output /Users/yuhan/PawWork; opened/collapsed the right panel; added Files/Review/Terminal right-panel tabs; pinned two sessions and drag-reordered them in the sidebar; verified the left sidebar toggle state after #880.
Broader app E2E note: a mixed targeted suite had stale expectations in e2e/commands/panels.spec.ts and e2e/status/status-popover.spec.ts after the #878/#880 right-panel titlebar changes; the release bump itself does not change those surfaces.

Screenshots or Recordings

Not required: no visible UI changes in this version bump. Manual Computer Use checks covered the release candidate UI paths listed above.

Checklist

• Type label — this PR carries exactly one of bug, enhancement, task, documentation. Type labels are author-added; the labeler bot does NOT assign them. Add the label in the GitHub UI, then tick this.
• Routing labels — this PR carries at least one of app, ui, platform, harness, ci. The labeler bot assigns these on PR open based on changed paths. Confirm the bot's choice (or override if wrong), then tick this.
• Priority label — this PR carries exactly one of P0, P1, P2, P3. The priority-triage bot suggests one on PR open. Confirm or override, then tick this.
• Human Review Status above is set to Pending, Approved by @<reviewer>, or Not required: <reason> (default is Pending; "not required" is restricted to bot-authored low-risk PRs).
• I linked the related issue, or stated in Summary why there is no issue.
• I described the review focus and any meaningful risks.
• I replaced the example block in How To Verify with the real verification steps and the key result for each.
• I did not introduce unrelated refactors, dependencies, generated files, or file changes beyond the stated scope.
• (conditional) I manually checked visible UI or copy changes when needed, with screenshots or recordings. Leave unticked only if no visible UI or copy changed.
• (conditional) I considered macOS and Windows impact for platform, packaging, updater, signing, paths, shell, or permissions changes. Leave unticked only if no platform/packaging surface was touched.
• (conditional) I called out docs, release notes, dependencies, permissions, credentials, deletion behavior, generated content, or local file changes when relevant. Leave unticked only if none of those surfaces was touched.
• I reviewed the final diff for unrelated changes and suspicious dependency changes.
• I am targeting dev, and my PR title and commit messages use Conventional Commits in English.

[coderabbitai]

Warning

Review limit reached

@Astro-Han, we couldn't start this review because you've used your available PR reviews for now.

Your plan currently allows 1 review/hour. Refill in 25 minutes and 55 seconds.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more review capacity refills, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 8e5822fc-c296-4f3d-bca7-784f10f7214b

📥 Commits

Reviewing files that changed from the base of the PR and between 87cc225 and d24dbb5.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• packages/desktop-electron/package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/release-v2026.5.25

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Suggested priority: P2 (includes non-doc, non-test paths outside the low-risk bucket).

P1/P0 are reserved for maintainer confirmation. Please relabel manually if this is a release blocker, security issue, data-loss risk, or updater/runtime failure.

[gemini-code-assist]

Code Review

This pull request updates the version of the @opencode-ai/desktop-electron package from 2026.5.23 to 2026.5.25 in both package.json and bun.lock. I have no feedback to provide.