Skip to content

chore(master): release 0.25.2 - #465

Merged
AprilNEA merged 1 commit into
masterfrom
release-please--branches--master--components--desktop
Aug 21, 2026
Merged

chore(master): release 0.25.2#465
AprilNEA merged 1 commit into
masterfrom
release-please--branches--master--components--desktop

Conversation

@arcbox-labs

@arcbox-labs arcbox-labs Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.25.2 (2026-08-21)

Bug Fixes

  • attachments: preserve original image filenames (#463) (c5e864b)
  • engine: reach model endpoints through fake-IP tunnels (f382df6)

This PR was generated with Release Please. See documentation.

@pullfrog pullfrog 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.

✅ 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.json moves "." from 0.25.1 to 0.25.2.
  • Package versionapps/desktop/package.json version matches at 0.25.2, which is what the build-desktop.yml tag gate compares against v${version} (Invariant 5).
  • Changelog entry — new 0.25.2 section listing the single fix(attachments): preserve original image filenames (#463), with the compare link rebased to v0.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.1 release commit 9c97594d, and it is a fix:, so a patch bump is correct.
  • Repo grep for 0.25.1 outside CHANGELOGs turns up only unrelated pnpm-lock.yaml entries (hermes-estree/hermes-parser@0.25.1). Root package.json staying at 0.0.0 and apps/mobile/app.json keeping its own expo.version are 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 that finalize-releases.yml will cut on the post-merge SHA.
  • git ls-remote --tags origin confirms v0.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.

Pullfrog  | View workflow run | Using Claude Opus𝕏

@arcbox-labs
arcbox-labs Bot force-pushed the release-please--branches--master--components--desktop branch from d59fbc6 to f442d46 Compare August 21, 2026 18:03
@AprilNEA
AprilNEA merged commit 4ec412d into master Aug 21, 2026
10 of 11 checks passed
@AprilNEA
AprilNEA deleted the release-please--branches--master--components--desktop branch August 21, 2026 18:07
@arcbox-labs

arcbox-labs Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant