chore: release v0.2.14

[Astro-Han]

Summary

Bump PawWork release package versions from 0.2.13 to 0.2.14.

Why

Prepare the next stable desktop release. Carries the session flow flicker fix from #251 (#248) so users sending prompts no longer see the route content briefly replaced by the Suspense fallback.

Related Issue

No linked issue. This is the release bump PR. Behavior changes shipping in this release: #248 (via #251).

How To Verify

bun install --frozen-lockfile

Screenshots or Recordings

Not applicable. No visible UI changes in this PR.

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

Release Notes

• Chores
  • Version bumped to 0.2.14 across all packages.

[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: 0d036249-e146-4321-96fe-1a76ef92ebf9

📥 Commits

Reviewing files that changed from the base of the PR and between b97ce51 and 3c63c8e.

⛔ 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). (11)

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

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 224
File: packages/app/src/i18n/zh.ts:0-0
Timestamp: 2026-04-24T17:08:44.294Z
Learning: In Astro-Han/pawwork PR `#224`, the first-occurrence `PawWork 爪印` branding rule originally specified in issue `#196` was superseded by an updated Chinese-branding spec. On all zh UI surfaces in `packages/app/src/i18n/zh.ts` (e.g., `dialog.model.unpaid.freeModels.title`, `session.new.subtitle`, `sidebar.gettingStarted.line1`), the correct and intentional target is fully localized `爪印` branding — no `PawWork` prefix. Do NOT flag these strings as missing the first-occurrence `PawWork 爪印` rule in future reviews.

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.

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 208
File: packages/app/src/components/prompt-input.tsx:1569-1611
Timestamp: 2026-04-24T05:39:56.086Z
Learning: In Astro-Han/pawwork `packages/app/src/components/prompt-input.tsx`, after the composer unification in PR `#208` (fixed in commit 5d810aa):
- `SendButton.disabled` does NOT gate on `store.mode !== "normal"`. Shell mode has a fully visible, clickable orange submit button that calls `handleSubmit` directly (same path as the Enter key in `handleKeyDown`). Do NOT suggest re-adding the mode gate.
- `SendButton` does NOT use the `buttons()` spring opacity animation (`style={buttons()}`). It is always fully visible regardless of mode.
- `WorkspaceChip` is gated on `props.homeMode && store.mode === "normal"` so it hides in shell mode (preventing it from appearing isolated/bright while neighboring controls fade).
- The left-side chip group (`aria-hidden={store.mode !== "normal"}`) covers attach/model/variant/workspace controls only; `SendButton` remains in a separate right-side sibling div.

🔇 Additional comments (4)

packages/opencode/package.json (1)

3-3: Version bump is correct and aligned with the release objective.
This change cleanly updates the package to 0.2.14 with no unintended manifest drift.

packages/app/package.json (1)

3-3: Looks good: package version updated as expected for the release.
No additional manifest changes were introduced in this segment.

packages/util/package.json (1)

3-3: Approved: util package version bump is clean and consistent.
This is an appropriate version-only release change.

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

4-4: Version update is correct for the desktop release package.
Line 4 is aligned with the 0.2.14 release cadence across packages.

---

📝 Walkthrough

Walkthrough

This pull request bumps the version number from 0.2.13 to 0.2.14 across four packages in the monorepo: @opencode-ai/app, @opencode-ai/desktop-electron, @opencode-ai/opencode, and @opencode-ai/util.

Changes

Cohort / File(s)	Summary
Version Bump packages/app/package.json, packages/desktop-electron/package.json, packages/opencode/package.json, packages/util/package.json	Incremented package version from 0.2.13 to 0.2.14 across all four packages.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: release v0.2.13 #249: Sequential version bump of the same packages (0.2.12→0.2.13 predecessor release).
• chore: bump desktop release to 0.2.12 #240: Performs identical version-bump changes across the same package.json files in the monorepo.
• chore: bump version to v0.2.4 #83: Modifies version fields for the same set of packages (app, desktop-electron, opencode, util).

Poem

🐰 Hop, hop, hooray! The numbers climb so high,
From .13 to .14, watch the versions fly!
Four little packages dressed in new release gear,
A bump, a hop, a git commit—la-di-dah! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: release v0.2.14' clearly and concisely describes the main change: a version bump release following Conventional Commits format.
Description check	✅ Passed	The description covers all required template sections with complete information: summary of changes, rationale, related issues with justification, verification steps, and a fully completed checklist.
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-14

---

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

[gemini-code-assist]

Code Review

This pull request updates the version of several packages, including @opencode-ai/app, @opencode-ai/desktop-electron, opencode, and @opencode-ai/util, from 0.2.13 to 0.2.14, along with the corresponding updates in the bun.lock file. I have no feedback to provide.