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

[Astro-Han]

Summary

Bump the desktop Electron package version from 2026.5.13 to 2026.5.15 so the release workflow will create v2026.5.15 assets.

Why

The current dev release candidate is green after the post-merge Windows advisory fix. The release workflow reads packages/desktop-electron/package.json to derive the GitHub Release tag and artifact version.

Related Issue

No related issue. This is the release version bump for v2026.5.15.

Human Review Status

Not required. Maintainer requested the release flow and this PR only changes the release version field.

Review Focus

Confirm the changed version is exactly 2026.5.15 and no other files are included.

Risk Notes

Low. This affects release metadata and artifact naming for the desktop release workflow. No runtime behavior, dependencies, generated files, or lockfiles changed.

How To Verify

Current dev CI: ci/codeql/desktop-smoke/windows-advisory all green on bf0c1397cc627e89e2a03a1a8ec6fe0625b6abe5
Dependency setup: bun install --frozen-lockfile completed in the release worktree
Version source: node -p "require('./packages/desktop-electron/package.json').version" -> 2026.5.15
Release verifier tests: bun --cwd packages/desktop-electron test scripts/verify-release.test.ts -> 31 passed, 0 failed
Diff check: packages/desktop-electron/package.json only, 1 insertion and 1 deletion

Screenshots or Recordings

Not applicable. No visible UI change.

Checklist

• Human review status is stated above as pending, approved, or not required
• I linked the related issue, or stated why there is no issue
• This PR has type, primary area, and priority labels, or I requested maintainer labeling
• I described the review focus and any meaningful risks
• I listed the relevant verification steps and the key result for each
• I did not introduce unrelated refactors, dependencies, generated files, or file changes beyond the stated scope
• I manually checked visible UI or copy changes when needed, with screenshots or recordings
• I considered macOS and Windows impact for platform, packaging, updater, signing, paths, shell, or permissions changes
• I called out docs, release notes, dependencies, permissions, credentials, deletion behavior, generated content, or local file changes when relevant
• 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

Rate limit exceeded

@Astro-Han has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 24 minutes and 36 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, 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 the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 5b60d9b9-d463-421e-8cbe-f5f5646feb38

📥 Commits

Reviewing files that changed from the base of the PR and between bf0c139 and 443d876.

📒 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-2026-5-15

---

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 in package.json from 2026.5.13 to 2026.5.15. There are no review comments to address, and I have no feedback to provide.