chore(master): release 0.25.2 - #465
Conversation
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — a release-please cut of desktop 0.25.2; three mechanical files with no behavioral surface, so the review is verification rather than code reading.
- Manifest bump —
.release-please-manifest.jsonmoves"."from0.25.1to0.25.2. - Package version —
apps/desktop/package.jsonversionmatches at0.25.2, which is what thebuild-desktop.ymltag gate compares againstv${version}(Invariant 5). - Changelog entry — new
0.25.2section listing the singlefix(attachments): preserve original image filenames(#463), with the compare link rebased tov0.25.1...v0.25.2.
Verification performed against head d59fbc67:
- All three files name the same version, and the bump size is right — exactly one commit landed since the
0.25.1release commit9c97594d, and it is afix:, so a patch bump is correct. - Repo grep for
0.25.1outside CHANGELOGs turns up only unrelatedpnpm-lock.yamlentries (hermes-estree/hermes-parser@0.25.1). Rootpackage.jsonstaying at0.0.0andapps/mobile/app.jsonkeeping its ownexpo.versionare both expected, not drift. git log origin/master --not HEAD^is empty, so the PR base is master HEAD — no undocumented commit rides into the tag thatfinalize-releases.ymlwill cut on the post-merge SHA.git ls-remote --tags originconfirmsv0.25.1(9c97594d) is the newest tag, so the changelog's compare link points at a tag that really exists.
One note on the release's content, not on this diff: the shipped fix c5e864b touches the wire protocol, taking WIRE_PROTOCOL_VERSION from 77 to 78 while leaving MIN_COMPATIBLE_WIRE_VERSION at 76. That is the correct pairing for an additive field, and it keeps 0.25.1 and 0.25.2 peers mutually compatible since both sit above the floor. No packaging, signing, or CI/toolchain files changed in this release window, so a release-desktop.yml dry_run dispatch is not warranted here.
Claude Opus | 𝕏
d59fbc6 to
f442d46
Compare
|
🤖 Created releases: 🌻 |

🤖 I have created a release beep boop
0.25.2 (2026-08-21)
Bug Fixes
This PR was generated with Release Please. See documentation.