chore(release): bump desktop version to 2026.6.12

[Astro-Han]

Summary

Bump the desktop release version to 2026.6.12.

Why

This prepares the next production desktop release after the changes merged since v2026.6.11.

Related Issue

No issue: release metadata bump for the v2026.6.12 production release.

Human Review Status

Not required: automated release metadata bump only.

Review Focus

Confirm this PR only updates the desktop package version and the matching lockfile workspace entry.

Risk Notes

No behavior changes. The visible UI/copy checklist item is not applicable because this PR only changes release metadata.

How To Verify

bun install --lockfile-only: updated bun.lock for the desktop workspace version.
bun install --frozen-lockfile: completed successfully in the release worktree.
git diff --check: passed with no whitespace errors.
Diff review: only packages/desktop-electron/package.json and bun.lock changed from 2026.6.11 to 2026.6.12.

Screenshots or Recordings

Not applicable: no visible UI or copy changes.

Checklist

How to use this checklist:

• Tick a box by replacing [ ] with [x]. Do not edit, add, or remove items.
• The bot-applied label items can only be honestly ticked AFTER the PR is opened and the labeler / priority-triage bots have run — return to the PR description and tick them then.
• Most items are required. The few that are conditional are explicitly marked (conditional); for those, leave unticked if they truly do not apply and explain why in Risk Notes. All other items must be ticked before requesting human review.

• 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 the desktop app version to 2026.6.12.

[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: a66ad6f1-d89b-4e28-9b5d-3aeb0029fa12

📥 Commits

Reviewing files that changed from the base of the PR and between a1fda26 and 68bd869.

⛔ 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.11 to 2026.6.12. No other files or fields are modified.

Changes

Desktop Electron Version Bump

Layer / File(s)	Summary
Package version update packages/desktop-electron/package.json	Bumps the version field from 2026.6.11 to 2026.6.12.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minutes

Possibly related PRs

• Astro-Han/pawwork#1338: Same single-field version bump in packages/desktop-electron/package.json (from 2026.6.6 to 2026.6.7).
• Astro-Han/pawwork#1356: Same single-field version bump in packages/desktop-electron/package.json (from 2026.6.7 to 2026.6.8).
• Astro-Han/pawwork#1185: Same single-field version bump in packages/desktop-electron/package.json (from 2026.6.2 to 2026.6.3).

Suggested labels

desktop

🐇 A tiny number flips with a hop,
From .11 to .12 — one small drop!
The package is fresh, the version is new,
A patch in the field, just a nudge or two.
🥕 On to the next build we go!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise, specific, and accurately summarizes the version bump release change.
Description check	✅ Passed	The description follows the template and includes the required summary, why, review status, risks, and verification details.
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-v2026.6.12

---

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

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