chore(master): release 0.26.1

[arcbox-labs]

🤖 I have created a release beep boop

0.26.1 (2026-08-24)

Bug Fixes

• agent-adapter,engine: stream codex rollout reads and evict expired history caches (#466) (fedc6ec)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

Updates the desktop application release metadata for version 0.26.1.

• Bumps the Release Please manifest and desktop package version from 0.26.0 to 0.26.1.
• Adds the 0.26.1 bug-fix entry to the desktop changelog.

Confidence Score: 5/5

The release metadata changes appear safe to merge.

The manifest, changelog, and authoritative desktop package version are aligned at 0.26.1, with no missing coordinated release update or concrete failure identified.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Advances the tracked release version to 0.26.1, aligned with the desktop package.
apps/desktop/CHANGELOG.md	Adds an internally consistent 0.26.1 release entry describing the included bug fix.
apps/desktop/package.json	Bumps the desktop package version to 0.26.1 for packaging and release automation.

_{Reviews (1): Last reviewed commit: "chore(master): release 0.26.1" | Re-trigger Greptile}

[pullfrog]

✅ No new issues found.

Reviewed changes — a stock release-please cut of the single managed package (., component desktop). No behavioral surface of its own, so this review is verification rather than code reading.

• .release-please-manifest.json — "." bumped 0.26.0 → 0.26.1.
• apps/desktop/package.json — version bumped 0.26.0 → 0.26.1 via the config's extra-files $.version write.
• apps/desktop/CHANGELOG.md — new ## [0.26.1] section with the compare link v0.26.0...v0.26.1.

Checks performed against head 2639d921:

• Version agreement and bump size are correct. All three files say 0.26.1, and the only commit between tag v0.26.0 (16411c91) and this PR's base is fedc6ec6 fix(agent-adapter,engine): … — a single fix: → patch.
• No stale version drift. grep -rn -F '0.26.0' across the repo excluding node_modules, .git, and *CHANGELOG.md returns zero hits (no pnpm-lock.yaml substring false positive this cut). Root package.json at 0.0.0 and apps/mobile/app.json expo.version at 1.0.0 are both by design, not drift.
• The compare link resolves. git ls-remote --tags origin confirms v0.26.0 exists at 16411c91, so the changelog's v0.26.0...v0.26.1 range is real.
• No undocumented riders. git log origin/master --not HEAD^ is empty, so the PR base is master HEAD — nothing extra will ride into the tag that finalize-releases.yml places on post-merge master.
• The one shipped fix carries no release-machinery risk. git diff --stat 16411c91...fedc6ec6 touches only packages/host/agent-adapter/src/native/codex/{adapter,history}.ts, packages/host/engine/src/session/history-service.ts, and three test files. No workflow, composite action, packaging script, or toolchain pin changed, so this release is not the first to exercise a reworked signing or packaging path — a release-desktop.yml dry_run: true dispatch isn't warranted here.

Mergeable as-is once CI is green on 2639d921.

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