Settings → About only showed v{pkg.version} (4.12.7-lotus): the same on web and desktop, and unchanged across many deploys a day. So "which build are you on?" had no answer, which matters for desktop updater reports.
Web:vite.config.js stamps the short commit and build time into the bundle (define). The commit comes from git rev-parse --short=8 HEAD; production builds from a git clone. LOTUS_BUILD_COMMIT overrides it, and without git it reads unknown. About shows "Web build <commit> · built <date>", with the commit linking to Gitea and the date in the user's locale. The values only land in the lazily loaded Settings chunk.
Desktop: also "Desktop <version>", read from Tauri's built-in plugin:app|version. That's the same command @tauri-apps/api's getVersion() uses, and cinny-desktop's core:default capability already allows it, so the desktop app needs no change.
Verified (local dev):
Web: Web build e1168f47 · built Oct 19, 2026, 3:23 PM; the commit matches HEAD and the link is …/LotusGuild/cinny/commit/e1168f47.
Desktop: with a stand-in Tauri bridge answering plugin:app|version → 4.12.377, About shows Desktop 4.12.377 above the web line.
I couldn't run a real desktop build here. The first desktop nightly after this merges is the real check.
Fixes #276.
Settings → About only showed `v{pkg.version}` (4.12.7-lotus): the same on web and desktop, and unchanged across many deploys a day. So "which build are you on?" had no answer, which matters for desktop updater reports.
- **Web:** `vite.config.js` stamps the short commit and build time into the bundle (`define`). The commit comes from `git rev-parse --short=8 HEAD`; production builds from a git clone. `LOTUS_BUILD_COMMIT` overrides it, and without git it reads `unknown`. About shows **"Web build `<commit>` · built `<date>`"**, with the commit linking to Gitea and the date in the user's locale. The values only land in the lazily loaded Settings chunk.
- **Desktop:** also **"Desktop `<version>`"**, read from Tauri's built-in `plugin:app|version`. That's the same command `@tauri-apps/api`'s `getVersion()` uses, and cinny-desktop's `core:default` capability already allows it, so the desktop app needs no change.
**Verified** (local dev):
- Web: `Web build e1168f47 · built Oct 19, 2026, 3:23 PM`; the commit matches HEAD and the link is `…/LotusGuild/cinny/commit/e1168f47`.
- Desktop: with a stand-in Tauri bridge answering `plugin:app|version` → `4.12.377`, About shows `Desktop 4.12.377` above the web line.
- I couldn't run a real desktop build here. The first desktop nightly after this merges is the real check.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
Settings → About only showed cinny's package version, the same on web
and desktop and unchanged across many deploys a day. vite.config.js now
stamps the short commit (git, or LOTUS_BUILD_COMMIT; "unknown" without
git) and build time into the bundle, and About shows "Web build <commit>
· built <date>", linking the commit. On desktop it also shows "Desktop
<version>" from Tauri's built-in plugin:app|version (allowed by
core:default).
Fixes#276
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #276.
Settings → About only showed
v{pkg.version}(4.12.7-lotus): the same on web and desktop, and unchanged across many deploys a day. So "which build are you on?" had no answer, which matters for desktop updater reports.vite.config.jsstamps the short commit and build time into the bundle (define). The commit comes fromgit rev-parse --short=8 HEAD; production builds from a git clone.LOTUS_BUILD_COMMIToverrides it, and without git it readsunknown. About shows "Web build<commit>· built<date>", with the commit linking to Gitea and the date in the user's locale. The values only land in the lazily loaded Settings chunk.<version>", read from Tauri's built-inplugin:app|version. That's the same command@tauri-apps/api'sgetVersion()uses, and cinny-desktop'score:defaultcapability already allows it, so the desktop app needs no change.Verified (local dev):
Web build e1168f47 · built Oct 19, 2026, 3:23 PM; the commit matches HEAD and the link is…/LotusGuild/cinny/commit/e1168f47.plugin:app|version→4.12.377, About showsDesktop 4.12.377above the web line.🤖 Generated with Claude Code
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5