chore: bump version to v0.2.3#78
Merged
Merged
Conversation
Re-release v0.2.3 after the prior dock-icon regression rollback. Bumps the four workspace packages tracked under the PawWork-managed 0.2.x line (desktop-electron, app, opencode, util) and refreshes bun.lock.
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
📝 WalkthroughWalkthroughFour package.json files updated with version bump from 0.2.2 to 0.2.3 across the monorepo packages: app, desktop-electron, opencode, and util. No configuration, dependencies, or scripts modified. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
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.2 to 0.2.3. The bun.lock file has also been updated to reflect these changes. I have no feedback to provide.
This was referenced Apr 21, 2026
11 tasks
Astro-Han
added a commit
that referenced
this pull request
May 13, 2026
Add PR0.3 perf diagnostics for the perf gate. Root cause / goal: - PR0.2 could block perf regressions, but a failing comparator still left too much manual artifact digging before a reviewer could explain the failure. - This PR adds the diagnostics layer: replayable failure evidence, terminal side-panel coverage, and a stable PR perf delta comment. Change boundary: - Add a terminal-side-panel-open perf scenario without changing product runtime behavior. - Add PR perf delta markdown rendering and compare-perf --comment-output support. - Update perf-probe-baseline to post or update one marker-based PR comment, confirm comparator failures before failing the job, and capture trace artifacts only after a confirmed regression. - Make Playwright trace mode controllable via PAWWORK_PERF_TRACE and keep base/head harness config aligned. Verification: - Typecheck passed: bun run typecheck. - Perf metrics tests passed: bun test --preload ./happydom.ts ./src/testing/perf-metrics.test.ts. - Local perf suite passed: bun --cwd packages/app test:e2e:local:perf. - Trace smoke passed with PAWWORK_PERF_TRACE=1. - Workflow lint passed after follow-up edits: actionlint .github/workflows/perf-probe-baseline.yml. - Latest PR checks passed, including perf-probe-baseline, typecheck, unit-app, unit-opencode, unit-desktop, smoke-macos-arm64, e2e-artifacts, and CodeQL. Review follow-ups: - Addressed the perf comparator false-fail risk by adding a no-trace confirmation run before trace capture and final failure. - Addressed base trace completeness by syncing packages/app/playwright.config.ts into the base checkout. - Addressed CodeRabbit's trigger-path comment by adding packages/app/playwright.config.ts to pull_request.paths and resolving the thread. Residual risk / deferred work: - This is CI harness and diagnostics only. It does not change product behavior or perf thresholds. - The remaining risk is workflow runtime cost when an initial comparator failure requires confirmation and trace reruns. Part of #600. Task anchor: task #78.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
desktop-electron,app,opencode,utilfrom 0.2.2 → 0.2.3 (the four PawWork-managed packages fromchore: renumber to 0.2.x6ed1474)bun.lockwith the new workspace versions; no other dependency changesWhy
Re-release v0.2.3 after the prior dock-icon regression rollback. Signing, notarization, and the
build.ymlpipeline have cleared the local smoke checklist, and the local upstream tag pool has been cleared so thatoriginonly carries the PawWork-ownedv0.2.2— reusingv0.2.3no longer collides with anything on the remote.Related Issue
No direct issue link. Internal-feedback P0 (memory bloat) cannot be reproduced without a packaged dmg, so it stays open and gets investigated against the v0.2.3 build. #21 (skill AskUserQuestion misfire) is deferred to a follow-up.
How To Verify
```bash
bun turbo typecheck
bun turbo test:ci
```
Local verification was skipped because this PR is a pure `version` string bump plus the matching `bun.lock` refresh — no executable code paths changed. The required CI checks (`ci`, `desktop-smoke`, `codeql`) will gate the merge.
Screenshots or Recordings
N/A — no UI changes.
Checklist
Summary by CodeRabbit