chore: bump to 2026.5.12

[Astro-Han]

Summary

• Bump the PawWork release version from 2026.5.11 to 2026.5.12.
• Match the previous v2026.5.11 release bump scope: app, desktop-electron, opencode, and util package manifests only.
• Sync the release-notes toast E2E fixture so its mocked release payload and version assertions reflect v2026.5.12.

Related Issue

Release workflow only. No linked issue.

Human Review Status

Pending. A human should make the final merge decision after reviewing the final diff and verification evidence.

Review Focus

• Confirm the version bump stays limited to the four package manifests.
• Confirm the release-notes fixture now anchors on v2026.5.12 everywhere the smoke paths expect the current app version.

Risk Notes

• The release-notes E2E file uses the app version string as its current-version anchor. Missing one replacement there would make the update-toast smoke fail after the bump.
• No product logic, dependencies, or release-body content changes are included here.

How To Verify

Targeted release-notes E2E: bunx playwright test e2e/release-notes/release-notes-toast.spec.ts -> 10 passed
Diff check: git diff --check -> pass

Screenshots or Recordings

Not applicable. This PR only bumps version manifests and aligns the release-notes smoke fixture.

Checklist

• Human review status is stated above as pending, approved, or not required
• I linked the related issue, or stated why there is no issue
• This PR has type, primary area, and priority labels, or I requested maintainer labeling
• I described the review focus and any meaningful risks
• I listed the relevant verification steps and the key result for each
• I did not introduce unrelated refactors, dependencies, generated files, or file changes beyond the stated scope
• I manually checked visible UI or copy changes when needed, with screenshots or recordings
• I considered macOS and Windows impact for platform, packaging, updater, signing, paths, shell, or permissions changes
• I called out docs, release notes, dependencies, permissions, credentials, deletion behavior, generated content, or local file changes when relevant
• 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
  • Version bumped to v2026.5.12 across the application and all packages.

[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: a1ac2d1c-7ed2-4e26-a99b-5a103d548c12

📥 Commits

Reviewing files that changed from the base of the PR and between 54c7661 and f56349a.

📒 Files selected for processing (5)

• packages/app/e2e/release-notes/release-notes-toast.spec.ts
• packages/app/package.json
• packages/desktop-electron/package.json
• packages/opencode/package.json
• packages/util/package.json

---

📝 Walkthrough

Walkthrough

This PR bumps the application and package versions from 2026.5.11 to 2026.5.12 across four package manifests and updates the corresponding release-notes toast e2e test fixtures and assertions to validate the new version.

Changes

Version 2026.5.12 Release

Layer / File(s)	Summary
Package Version Declarations packages/app/package.json, packages/desktop-electron/package.json, packages/opencode/package.json, packages/util/package.json	All four package manifests incremented from 2026.5.11 to 2026.5.12.
Release Notes Toast E2E Test packages/app/e2e/release-notes/release-notes-toast.spec.ts	Mocked GitHub release payloads' tag_name values and all test assertions (toast title, localStorage "seen" version, opened URL) updated to expect v2026.5.12, including English and Chinese (zh) localized variants across smoke, close, action, Escape, suppression, multi-version, and language fallback scenarios.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Astro-Han/pawwork#530: Prior version bump PR that advanced packages to 2026.5.11.
• Astro-Han/pawwork#488: Earlier PR that introduced the release-notes toast e2e test structure being updated here.
• Astro-Han/pawwork#364: Earlier package version bump PR following the same pattern.

Suggested labels

ci, P2, desktop

Poem

🐰 From five-dot-eleven hops to twelve so fine,
Each package thumps with version signs—
Toast tests now see the newest light,
Assertions dance with zh-flavored might,
A patch release, delightfully bright! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: bump to 2026.5.12' clearly and concisely describes the primary change: a version bump to 2026.5.12 across package manifests and release-notes fixtures.
Description check	✅ Passed	The description comprehensively covers all required template sections including summary, rationale, review focus, risks, verification steps, and a completed checklist matching the repository's pull request template.
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 docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/release-2026-5-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 and usage tips.}

[gemini-code-assist]

Code Review

This pull request updates the project version from 2026.5.11 to 2026.5.12 across multiple package.json files and synchronizes the end-to-end test expectations in the release notes toast specification to reflect this change. I have no feedback to provide as there were no review comments to evaluate.