chore: bump desktop release to 0.2.11

[Astro-Han]

Summary

Bump the PawWork desktop release version from 0.2.10 to 0.2.11 across the desktop package, app package, opencode package, util package, and lockfile workspace metadata.

Why

Prepare the next stable desktop release after the five PRs merged since v0.2.10.

Related Issue

No linked issue. This is release preparation for v0.2.11.

How To Verify

bun install --frozen-lockfile
node -p "require('./packages/desktop-electron/package.json').version"
bun test scripts/verify-release.test.ts # from packages/desktop-electron
bun test scripts/release-metadata-contract.test.ts scripts/release-workflow-contract.test.ts electron-builder-app-update.test.ts # from packages/desktop-electron
git diff --check

Screenshots or Recordings

N/A. Version bump only, no visible UI change.

Checklist

• I linked the related issue, or stated why there is no issue
• This PR has type, scope, and priority labels, or I requested maintainer labeling
• I listed the relevant verification steps, including tests when behavior changed
• I manually checked visible UI or copy changes when needed, with screenshots or recordings
• I considered macOS and Windows impact for desktop, packaging, updater, signing, paths, shell, or permissions changes
• I called out docs, release notes, dependencies, permissions, credentials, deletion behavior, or generated/local file changes when relevant
• I am targeting dev, and my PR title and commit messages use Conventional Commits in English

Summary by CodeRabbit

• Chores
  • Updated version to 0.2.11.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 2db0d1c8-d305-49f2-81bf-ac9460c0cc4c

📥 Commits

Reviewing files that changed from the base of the PR and between 06fd278 and 60de389.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (4)

• packages/app/package.json
• packages/desktop-electron/package.json
• packages/opencode/package.json
• packages/util/package.json

📜 Recent review details

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (12)

• GitHub Check: smoke-macos-arm64
• GitHub Check: unit-windows-opencode-server-tools
• GitHub Check: unit-windows-opencode-session
• GitHub Check: unit-windows-opencode-config-project
• GitHub Check: unit-windows-desktop
• GitHub Check: unit-windows-app
• GitHub Check: unit-opencode
• GitHub Check: unit-desktop
• GitHub Check: unit-app
• GitHub Check: typecheck
• GitHub Check: analyze-js-ts
• GitHub Check: e2e-artifacts

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 126
File: packages/ui/src/theme/context.tsx:11-16
Timestamp: 2026-04-22T09:32:58.310Z
Learning: In Astro-Han/pawwork (`packages/ui/src/theme/context.tsx` and related files), the renaming of localStorage theme keys from `opencode-*` to `pawwork-*` (THEME_ID, COLOR_SCHEME, THEME_CSS_LIGHT, THEME_CSS_DARK) is intentional and should NOT include a migration path from the old keys. Migrating would re-couple PawWork and OpenCode browser storage namespaces, which the PR is explicitly designed to avoid. A reset to the PawWork default theme on upgrade is acceptable by design.

🔇 Additional comments (4)

packages/opencode/package.json (1)

3-3: LGTM! Version bump is correct.

The version increment from 0.2.10 to 0.2.11 is consistent with the other packages in this release.

packages/app/package.json (1)

3-3: LGTM! Version bump is correct.

The version increment from 0.2.10 to 0.2.11 aligns with the coordinated release across all packages.

packages/desktop-electron/package.json (1)

4-4: LGTM! Desktop package version bump is correct.

The version increment from 0.2.10 to 0.2.11 is properly applied to the main desktop package.

packages/util/package.json (1)

3-3: LGTM! Version bump is correct.

The version increment from 0.2.10 to 0.2.11 is consistent with the coordinated release.

---

📝 Walkthrough

Walkthrough

A patch version bump across four monorepo packages from 0.2.10 to 0.2.11. All package manifests are updated with no changes to dependencies, exports, scripts, or configurations.

Changes

Cohort / File(s)	Summary
Package version bump packages/app/package.json, packages/desktop-electron/package.json, packages/opencode/package.json, packages/util/package.json	Version incremented from 0.2.10 to 0.2.11 across all packages.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: bump version to v0.2.4 #83: Identical version-bump changes across the same four package.json files.
• chore: bump version to v0.2.5 #119: Same package version-bump pattern applied to app, desktop-electron, opencode, and util packages.
• chore: bump version to v0.2.3 #78: Concurrent version field updates in the same package manifests.

Suggested labels

P1

Poem

🐰 Versions dance from ten to eleven,
Four little packages, climbing to heaven,
0.2.10 bids its farewell,
0.2.11 rings the bell! 🔔

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the main change: a version bump of the desktop release to 0.2.11 across multiple packages.
Description check	✅ Passed	The description is comprehensive and follows the template with all required sections completed, including summary, rationale, verification steps, and checklist confirmation.
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 chore/release-v0-2-11

---

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

[gemini-code-assist]

Code Review

This pull request updates the version from 0.2.10 to 0.2.11 for several packages in the monorepo. However, the version bump is incomplete as internal dependencies like @opencode-ai/sdk and @opencode-ai/shared were not updated, which may lead to workspace inconsistencies.