chore: bump version to 2026.5.1

[Astro-Han]

Summary

Bump PawWork package versions from 2026.4.29 to 2026.5.1 for the next stable desktop release.

Changes

• Updated packages/app, packages/opencode, packages/util, and packages/desktop-electron package versions to 2026.5.1.
• Updated bun.lock workspace package metadata to match.

Verification

• bun install --frozen-lockfile
• bun --cwd packages/desktop-electron test scripts/release-workflow-contract.test.ts scripts/electron-builder-app-update.test.ts
• git diff --check
• bun run --cwd packages/desktop-electron typecheck:release

Summary by CodeRabbit

• Chores
  • Updated package versions from 2026.4.29 to 2026.5.1 across all packages.

[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 2026.4.29 to 2026.5.1. The bun.lock file has also been updated to reflect these changes. I have no feedback to provide.

[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: ff5d975d-1c8f-448d-a5af-6b3be79223d0

📥 Commits

Reviewing files that changed from the base of the PR and between 0c8ca56 and 50d6b7a.

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

• GitHub Check: unit-windows-opencode-config-project
• GitHub Check: unit-windows-opencode-server-tools
• GitHub Check: unit-windows-opencode-session
• GitHub Check: unit-windows-desktop
• GitHub Check: unit-windows-app
• GitHub Check: unit-opencode
• GitHub Check: smoke-macos-arm64

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 270
File: packages/opencode/src/file/ripgrep.ts:311-328
Timestamp: 2026-04-28T05:36:18.200Z
Learning: In `packages/opencode/src/file/ripgrep.ts` (Astro-Han/pawwork, PR `#270`), the ripgrep binary download flow (`HttpClientRequest.get` → `fs.writeWithDirs` → `extract`) does NOT verify a pinned SHA-256 checksum. Adding per-platform hash verification (15.1.0 × 6 platforms) requires a dedicated manifest + `crypto.subtle.digest` step and is intentionally deferred to a follow-up PR. Existing mitigations: (1) `VERSION` is pinned to `"15.1.0"`, (2) downloads are over HTTPS from GitHub Releases, (3) PawWork production builds ship a bundled `rg` binary so this download path is a last-resort fallback (system PATH → cached → download). Do NOT re-flag the missing checksum verification in this file until the dedicated follow-up PR lands.

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 224
File: packages/app/src/i18n/zh.ts:0-0
Timestamp: 2026-04-24T17:08:46.780Z
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: 270
File: packages/opencode/src/tool/edit.ts:48-48
Timestamp: 2026-04-28T08:14:31.436Z
Learning: In `packages/opencode/src/tool/edit.ts` (Astro-Han/pawwork), the `filePath` schema description (`"The absolute path to the file to modify"`) is upstream-inherited from `dev:packages/opencode/src/tool/edit.ts:48`. The runtime actually accepts relative paths (resolved via `Instance.directory` at lines 79-81), but the description fix is intentionally deferred to a single PawWork-authored description-cleanup PR that will also cover the identical mismatch in `packages/opencode/src/tool/write.ts:24`. Do NOT re-flag the too-narrow `filePath` description in upstream-sync PRs; flag it only in the dedicated description-cleanup PR.

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 270
File: packages/opencode/src/patch/index.ts:337-346
Timestamp: 2026-04-28T04:38:05.946Z
Learning: In Astro-Han/pawwork (`packages/opencode/src/patch/index.ts`), the BOM-transition surfacing gap — where `Bom.split` strips BOM before building `unified_diff`/`new_content` but `Bom.join` later re-attaches BOM on disk write, meaning BOM changes are not reflected in the diff payload — is intentionally deferred. PR `#270` is an upstream-sync graft; fixing the issue here would mix refactor + bugfix intents and drift the diff from the upstream baseline needed for clean future grafts. A dedicated follow-up PR (or upstream report) will address this. Do NOT re-flag the missing BOM-change surfacing in `ApplyPatchFileUpdate`/`ApplyPatchFileChange` as a blocking issue in PR `#270` or in future sync PRs that carry the same upstream baseline.

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: 346
File: packages/app/src/pages/session.tsx:2071-2071
Timestamp: 2026-04-30T14:25:19.902Z
Learning: In `packages/app/src/pages/session.tsx` (Astro-Han/pawwork), the session-panel container uses `min-w-[24rem]` unconditionally (no `md:` prefix). This is intentional: PawWork is Electron-only and PR `#346` raises `minWidth` in `packages/desktop-electron/src/main/windows.ts` from 480 → 768px, which matches the Tailwind `md` breakpoint. Windows narrower than 768px are unreachable in production, so there is no narrow-viewport flex-col case to guard against. Do NOT suggest scoping this `min-w-[24rem]` to `md:` in future reviews.

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 270
File: packages/opencode/src/tool/edit.ts:35-45
Timestamp: 2026-04-28T04:38:11.727Z
Learning: In `packages/opencode/src/tool/edit.ts` (Astro-Han/pawwork, PR `#270`), the module-scoped `Map<string, Semaphore.Semaphore>` (`locks`) and `lock(filePath)` helper are intentionally left as a global, never-cleaned registry. PR `#270` is a pure upstream-sync graft and mixing in a bugfix would drift the diff from the upstream baseline. The fix (moving per-file semaphores into `InstanceState`/`ScopedCache` for per-instance lifecycle management) is tracked as a follow-up to land in its own PR or be reported upstream. Do NOT re-flag the absence of InstanceState wiring for the lock map in this file until the follow-up PR is opened.

🔇 Additional comments (4)

packages/opencode/package.json (1)

3-3: LGTM! Version bump is correct.

The version update from 2026.4.29 to 2026.5.1 is consistent with the PR objectives for the desktop release.

packages/util/package.json (1)

3-3: LGTM! Version bump is correct.

The version update from 2026.4.29 to 2026.5.1 aligns with the coordinated workspace version bump.

packages/app/package.json (1)

3-3: LGTM! Version bump is correct.

The version update from 2026.4.29 to 2026.5.1 is consistent with the release version bump.

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

4-4: LGTM! Version bump is correct.

The version update from 2026.4.29 to 2026.5.1 completes the synchronized workspace version bump for the desktop release.

---

📝 Walkthrough

Walkthrough

Package version updates are applied across four packages, bumping from 2026.4.29 to 2026.5.1. Only the version field in each package.json is modified; no dependencies, scripts, or other configuration are altered.

Changes

Cohort / File(s)	Summary
Version bump packages/app/package.json, packages/desktop-electron/package.json, packages/opencode/package.json, packages/util/package.json	Version field updated from 2026.4.29 to 2026.5.1 in all package manifests.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• pawwork#249 — Identical version bumps applied to the same four package.json files.
• pawwork#207 — Same package.json version field updates across the same set of packages.
• pawwork#78 — Matching version bump pattern in packages/app, packages/desktop-electron, packages/opencode, and packages/util.

Poem

🐰 Hop, hop, hooray! A new release springs forth,
Version numbers climb from south to north,
Five packages dressed in fresh 2026.5.1 attire,
The bump is done, the code's inspired! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description includes Summary, Changes, and Verification sections, but is missing several required template sections (Why, Related Issue, Review Focus, Risk Notes, and Checklist).	Complete the description by adding the missing template sections: Why (context/goal), Related Issue link, Review Focus, Risk Notes, and the verification Checklist to align with repository standards.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: bumping package versions to 2026.5.1 across multiple packages.
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-2026-5-1

---

_{Review rate limit: 2/3 reviews remaining, refill in 20 minutes.}

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