chore(master): release 0.25.1

[arcbox-labs]

🤖 I have created a release beep boop

0.25.1 (2026-08-20)

Bug Fixes

• assets: update aigateway to 0.6.0 (#461) (5673022)

---

This PR was generated with Release Please. See documentation.

[pullfrog]

✅ No new issues found.

Reviewed changes — the automated release-please cut of desktop 0.25.1. Three mechanical files, no behavioral surface of its own, so this review is verification rather than code reading.

• .release-please-manifest.json — "." bumped 0.25.0 → 0.25.1.
• apps/desktop/package.json — $.version bumped to 0.25.1 via the config's extra-files entry.
• apps/desktop/CHANGELOG.md — new 0.25.1 section with the compare link v0.25.0...v0.25.1.

Verification performed:

• Version agreement and bump size. All three files name 0.25.1. Exactly one commit has landed since the 0.25.0 release commit eac65e8f — 5673022 fix(assets): update aigateway to 0.6.0 (#461) — and fix: correctly yields a patch bump.
• No stale version references. Repo-wide grep for 0.25.0 outside changelogs returns only pnpm-workspace.yaml:199-200, the unrelated esbuild@<=0.24.2: ^0.25.0 security override. Root package.json stays 0.0.0 and apps/mobile/app.json keeps its own unmanaged expo.version — neither is drift.
• No undocumented riders. git log origin/master --not HEAD^ is empty, so the PR base is master HEAD and the only commit shipping in this release is the one already listed in the changelog. Nothing rides in invisibly.
• The compare link points at a real tag. v0.25.0 exists on the remote at eac65e8f, so v0.25.0...v0.25.1 resolves correctly.
• What actually ships. 5673022 bumps AIGATEWAY_VERSION in packages/host/assets/src/catalog.ts from 0.5.0-rc2 to 0.6.0 along with all five per-platform SRI digests and sizes — worth noting this is the first stable (non-rc) aigateway pin the desktop app ships. Digest and URL-template verification belonged to #461; no stale 0.5.x references remain under packages/host/assets/src/.

Packaging and signing workflows are unchanged since 0.25.0 shipped, so this release exercises no new release machinery and a dry_run dispatch is not warranted.

  ^{｜ View workflow run ｜ Using Claude Opus ｜ 𝕏}