chore(master): release 0.28.0

[arcbox-labs]

🤖 I have created a release beep boop

0.28.0 (2026-08-27)

Features

• mobile: add remote push notifications (#386) (53b6420)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

This automated release PR advances LinkCode Desktop from 0.27.0 to 0.28.0.

• Updates the Release Please manifest and desktop package version.
• Adds the 0.28.0 changelog entry for remote mobile push notifications.

Confidence Score: 5/5

The PR appears safe to merge because its release metadata is internally consistent with the repository’s desktop release and packaging flow.

The desktop package version remains the authoritative source for release-tag validation, artifact naming, and runtime version reporting, and the accompanying manifest and changelog changes align with it.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Advances the root Release Please release marker to 0.28.0, consistently with the configured desktop release flow.
apps/desktop/CHANGELOG.md	Adds the correctly versioned 0.28.0 release entry and comparison link.
apps/desktop/package.json	Advances the desktop application's authoritative package version to 0.28.0.

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

[pullfrog]

✅ No new issues found.

Reviewed changes — the release-please cut of 0.28.0 for the desktop component, verified mechanically rather than read as code.

• Version bump consistency — .release-please-manifest.json, apps/desktop/package.json, and the new apps/desktop/CHANGELOG.md section all name 0.28.0.
• Bump size — the only commit since v0.27.0 (2d66882c) is 53b64207 feat(mobile): add remote push notifications (#386); a feat: under bump-minor-pre-major is a minor, so 0.27.0 → 0.28.0 is right.
• Changelog link — v0.27.0...v0.28.0 resolves; git ls-remote --tags origin shows v0.27.0 at 2d66882c.
• No stale references — repo-wide grep for 0.27.0 excluding CHANGELOGs hits only pnpm-lock.yaml's unrelated scheduler@0.27.0.
• No undocumented riders — git log --oneline origin/master --not HEAD^ is empty, so the PR base is master HEAD and nothing beyond #386 ships in this tag.

ℹ️ The release exercises no new packaging machinery, and its user-visible content is mobile-only

git diff --stat 2d66882c...HEAD^ shows the shipped work is 15 files under apps/mobile plus locale additions in packages/presentation/i18n/src/locales/{en,zh-cn}.ts — no workflow, composite action, packaging script, or toolchain pin. So no release-desktop.yml dry_run: true rehearsal is needed before tagging; the signed build path is unchanged from v0.27.0.

Two things worth being aware of rather than acting on: the desktop artifact gains only the i18n strings from #386 despite the changelog headline reading mobile: add remote push notifications (the commit escaped exclude-paths precisely because it touched shared i18n), and the mobile app itself is not released by this tag — apps/mobile/app.json keeps its own unmanaged expo.version (1.0.0), deliberately outside this release train.

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