chore(release): bump desktop version to 2026.6.8

[Astro-Han]

Summary

Bumps the PawWork desktop release version from 2026.6.7 to 2026.6.8. There is no related issue; this is the release bump for the next stable desktop publish.

Why

dev has accumulated release-bound changes since v2026.6.7, and the desktop package version needs to advance before the release workflows build and publish the new installers.

Related Issue

No issue. Release bump only.

Human Review Status

Not required: automated release version bump only.

Review Focus

Confirm the diff is limited to the desktop package version and matching bun.lock workspace metadata.

Risk Notes

No product behavior changes. Packaging/update metadata is touched only through the version number. No visible UI or copy changed, so no screenshot or recording is included.

Skipped checklist items:

• Visible UI or copy check: no visible UI or copy changed.

How To Verify

bun install --frozen-lockfile: completed in a fresh release worktree.
bun install --lockfile-only: updated bun.lock for the new workspace version.
bun install --frozen-lockfile: checked the updated lockfile with no further changes.
git diff --check: passed.
Version check: packages/desktop-electron/package.json reads 2026.6.8.

Screenshots or Recordings

Not applicable. No visible UI or copy changed.

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.

Summary by CodeRabbit

• Chores
  • Updated package version to 2026.6.8.

[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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: e31bc2f0-673c-4551-a197-7bdf27a75e90

📥 Commits

Reviewing files that changed from the base of the PR and between f1f3d1a and af1bb69.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• packages/desktop-electron/package.json

---

📝 Walkthrough

Walkthrough

The version field in packages/desktop-electron/package.json is incremented from 2026.6.7 to 2026.6.8. No other files, dependencies, or metadata are modified.

Changes

Desktop Electron Version Bump

Layer / File(s)	Summary
Package version field packages/desktop-electron/package.json	version field updated from 2026.6.7 to 2026.6.8.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

• Astro-Han/pawwork#1338: Same single-field version bump in packages/desktop-electron/package.json (2026.6.6 → 2026.6.7), the direct predecessor release.
• Astro-Han/pawwork#1208: Same pattern — version-only bump of @opencode-ai/desktop-electron in packages/desktop-electron/package.json (2026.6.3 → 2026.6.4).
• Astro-Han/pawwork#1185: Identical change scope — bumps @opencode-ai/desktop-electron version in packages/desktop-electron/package.json with no other modifications (2026.6.2 → 2026.6.3).

Poem

🐇 A tiny hop, a version leaps,
From .7 to .8 the rabbit creeps,
One line changed, the json gleams,
Small but mighty, or so it seems!
thump thump — release day dreams! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: a version bump to the desktop package from 2026.6.7 to 2026.6.8.
Description check	✅ Passed	The PR description comprehensively addresses all required sections: Summary, Why, Related Issue, Human Review Status, Review Focus, Risk Notes, How To Verify, Screenshots/Recordings, and a complete Checklist with all applicable items ticked.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/release-2026.6.8

---

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.}