Skip to content

chore(release): bump desktop version to 2026.6.13 - #1483

Merged
Astro-Han merged 1 commit into
devfrom
claude/release-2026-6-13
Jun 29, 2026
Merged

chore(release): bump desktop version to 2026.6.13#1483
Astro-Han merged 1 commit into
devfrom
claude/release-2026-6-13

Conversation

@Astro-Han

Copy link
Copy Markdown
Owner

Summary

Bump the desktop release metadata to 2026.6.13 so the two user-facing fixes
already merged to dev ship in a stable release:

  • #1481 — sidebar drag now has a movement threshold, so clicks are no longer eaten by hand jitter.
  • #1482 — the Skills surface gets an Open skills folder action.

Change boundary

  • packages/desktop-electron/package.json: 2026.6.122026.6.13.
  • bun.lock: sync the matching workspace package version (only the version line changes).

Verification

  • bun install --frozen-lockfile completed in the release worktree.
  • bun install --lockfile-only updated the lockfile; git diff is exactly the two version lines.
  • git diff --check passed.

Release build (submit/finalize/Windows), publish, R2 mirror, and post-release
verification follow .github/RELEASE_CHECKLIST.md after this merges.

Bump the desktop release metadata to 2026.6.13 to ship the sidebar drag
fix (#1481) and the Skills folder entry (#1482) to users.

Change boundary:
- Update packages/desktop-electron/package.json from 2026.6.12 to 2026.6.13.
- Sync the matching bun.lock workspace package version.

Verification:
- bun install --frozen-lockfile completed in the release worktree.
- bun install --lockfile-only updated the lockfile (only the version line changed).
- git diff --check passed.
@Astro-Han Astro-Han added ci Continuous integration / GitHub Actions P0 Blocking / highest priority platform Electron shell, OS integration, packaging, updater, signing, paths, and permissions task Narrow execution, audit, spike, migration, tracking, or upstream follow-up work labels Jun 29, 2026
@coderabbitai

coderabbitai Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@Astro-Han, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 1 minute

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 87d169f0-14b1-4ec4-b587-849e6f06ab17

📥 Commits

Reviewing files that changed from the base of the PR and between 669fca3 and 8ddfa04.

⛔ Files ignored due to path filters (1)
  • bun.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • packages/desktop-electron/package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/release-2026-6-13

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

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested priority: P2 (includes non-doc, non-test paths outside the low-risk bucket).

P1/P0 are reserved for maintainer confirmation. Please relabel manually if this is a release blocker, security issue, data-loss risk, or updater/runtime failure.

@Astro-Han
Astro-Han merged commit 456ca9d into dev Jun 29, 2026
44 of 48 checks passed
@Astro-Han
Astro-Han deleted the claude/release-2026-6-13 branch June 29, 2026 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci Continuous integration / GitHub Actions P0 Blocking / highest priority platform Electron shell, OS integration, packaging, updater, signing, paths, and permissions task Narrow execution, audit, spike, migration, tracking, or upstream follow-up work

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant