chore(master): release 0.30.0 - #499
Conversation
Greptile SummaryUpdates the desktop release metadata to version 0.30.0.
Confidence Score: 5/5The release metadata update appears safe to merge. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| .release-please-manifest.json | Advances the root release-please version from 0.29.0 to 0.30.0. |
| apps/desktop/CHANGELOG.md | Adds the generated 0.30.0 release notes and comparison link. |
| apps/desktop/package.json | Updates the desktop application package version to 0.30.0. |
Reviews (3): Last reviewed commit: "chore(master): release 0.30.0" | Re-trigger Greptile
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — the automated release-please cut of 0.29.1. Three mechanical files, no behavioral surface of their own, so this review is verification rather than code reading.
- Version bump is consistent —
.release-please-manifest.json,apps/desktop/package.json, and the newapps/desktop/CHANGELOG.mdheading all name0.29.1. - Bump size matches the commits — exactly one commit since
v0.29.0(dee76ee fix(mobile): surface ambiguous deletion transport (#498)), a singlefix:→ patch. Correct. - No stale version references — a repo-wide grep for
0.29.0excluding CHANGELOGs returns onlypnpm-lock.yaml:2083,2142(kysely: ^0.28.5 || ^0.29.0), which are dependency ranges rather than pins. - No undocumented riders —
git log --oneline origin/master --not HEAD^is empty, confirming the PR base is master HEAD, so nothing ships that the changelog omits. - Compare link resolves —
v0.29.0exists on the remote atfdf70588, matching thechore(master): release 0.29.0 (#491)commit.
ℹ️ The desktop artifact gains almost nothing from this release
The sole shipped commit dee76ee touches apps/mobile/src/** plus two locale files, and the added deleteUnknown string sits under the mobile account-deletion namespace. Its appearance in the desktop changelog is correct rather than an exclude-paths bug — the commit also touches shared packages/presentation/i18n, which is not an excluded path — but no desktop-visible behavior changes here. Flagging only so the release is cut with accurate expectations; nothing to change.
ℹ️ No new release machinery is exercised, so no dry run is needed
Worth stating explicitly since it is the usual reason to hold a release PR: dee76ee touches no .github/workflows, composite action, packaging script, or toolchain pin. The signed build path for 0.29.1 is byte-for-byte the same machinery that produced 0.29.0, so a release-desktop.yml dry_run: true dispatch is not warranted before merging this one.
Claude Opus | 𝕏
a7dd0da to
50eb641
Compare
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — release-please force-replaced the previously reviewed 0.29.1 cut (a7dd0da) with a 0.30.0 cut after 317b14e feat(providers): resolve LinkCode Gateway as a claude-code-native endpoint (#503) landed on master. Still three mechanical files with no behavioral surface of their own, so this is verification rather than code reading.
- Rebumped patch → minor —
.release-please-manifest.json,apps/desktop/package.json, and the newapps/desktop/CHANGELOG.mdheading all name0.30.0.release-please-config.jsonsetsbump-minor-pre-major: true, so the incomingfeat:forces a minor even pre-1.0; the earlier0.29.1patch cut was correctly superseded rather than stacked on. - Replaced the abandoned changelog section — the
0.29.1heading was rewritten in place rather than left stranded above the new one, and a repo-wide grep for0.29.1excluding CHANGELOGs returns zero hits, so nothing half-wrote the abandoned cut. - Added the feature entry — the new section lists both commits since
v0.29.0(#503under Features,#498under Bug Fixes), which is the complete set. - Compare link rebased correctly —
git ls-remote --tags originshowsv0.29.0atfdf70588and nov0.29.1, sov0.29.0...v0.30.0points at the last really-tagged version. - No undocumented riders, no stale versions —
git log --oneline origin/master --not HEAD^is empty, confirming the PR base is master HEAD; a grep for0.29.0excluding CHANGELOGs returns onlypnpm-lock.yaml:2083,2142(kysely: ^0.28.5 || ^0.29.0), which are dependency ranges rather than pins.
ℹ️ This cut, unlike the abandoned one, does carry desktop-visible behavior
Worth correcting the note from the prior review: 0.29.1 would have shipped essentially nothing to desktop, but 317b14e changes provider resolution in packages/foundation/providers/src/catalog.ts so the LinkCode Gateway resolves as a claude-code-native endpoint. That is a real desktop-facing change and the reason the minor bump is right. Nothing to change — flagging only so the release is cut with accurate expectations.
ℹ️ Still no new release machinery, so no dry run is needed
git diff --stat fdf70588...HEAD^ covers 9 files, all under apps/mobile/src/**, packages/foundation/providers/src/**, packages/host/engine/src/__tests__/**, and packages/presentation/i18n/src/locales/**. No .github/workflows, composite action, packaging script, or toolchain pin moved, so the signed build path for 0.30.0 is the same machinery that produced 0.29.0 and a release-desktop.yml dry_run: true dispatch is not warranted before merging.
Claude Opus | 𝕏
50eb641 to
213fb72
Compare
213fb72 to
ee98e85
Compare
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — release-please recut the branch twice more since the previously reviewed 50eb641, first adding #500 and then #502 while rebasing onto the current master HEAD. Still the same three mechanical files with no behavioral surface of their own, so this is verification rather than code reading.
- Two changelog entries added —
fix(ui): make command palette instant (#500)under Bug Fixes andfeat(ui): refine thread hover feedback (#502)under Features. The version stays0.30.0:#502is afeat:and the cut was already minor, so it folds in without a rebump. - Changelog is now complete against master — the four entries are exactly the four commits between
fdf70588(v0.29.0) and135a5565(master HEAD):dee76ee,317b14e,16767b2,135a556. Nothing omitted, nothing invented. - Version still agrees across all three files —
.release-please-manifest.json,apps/desktop/package.json, and theCHANGELOG.mdheading all name0.30.0, and the compare linkv0.29.0...v0.30.0still points at the last really-tagged version (git ls-remote --tags originhasv0.29.0atfdf70588and nov0.29.1). - No undocumented riders, no stale or abandoned versions —
git log --oneline origin/master --not <head>^is empty against the current head, confirming the PR base is master HEAD.git grep 0.29.1returns zero hits, and a repo-wide0.29.0grep excluding CHANGELOGs returns onlypnpm-lock.yaml:2080,2142(kysely: ^0.28.5 || ^0.29.0), which are dependency ranges rather than pins.
ℹ️ The PR head moved again mid-review, so the findings are pinned to ee98e857
The pull_request event that triggered this run carried head_sha 213fb72, but the branch had already been force-replaced with ee98e857 (parent 135a5565) by the time the checkout ran — the third and fourth cuts landed roughly a minute apart. Everything above was re-verified against ee98e857; there is nothing to change, but if a fifth cut lands before merge the version-agreement and rider checks are worth repeating against that head rather than this one.
ℹ️ Still no new release machinery, so no dry run is needed
git diff --stat fdf70588...135a5565 covers 16 files under apps/mobile/src/**, packages/client/workbench/**, packages/foundation/providers/**, packages/host/engine/src/__tests__/**, packages/presentation/i18n/src/locales/**, packages/presentation/ui/src/shell/**, plus pnpm-lock.yaml. No .github/workflows, composite action, packaging script, or toolchain pin moved — 16767b2 only removes a dependency line from packages/client/workbench/package.json. The signed build path for 0.30.0 is the same machinery that produced 0.29.0, so a release-desktop.yml dry_run: true dispatch is not warranted before merging.
Claude Opus | 𝕏
|
🤖 Created releases: 🌻 |

🤖 I have created a release beep boop
0.30.0 (2026-09-03)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.