From 68367cb3a3f2166392e1d63c7c622a2de4f68e74 Mon Sep 17 00:00:00 2001 From: ScreenTinker Date: Fri, 12 Jun 2026 08:09:19 -0500 Subject: [PATCH] fix(settings): show the real app version in the About section (#83) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The settings "About" section hardcoded "ScreenTinker v1.4.1", so it never reflected the running build (#/admin already showed the correct version). Fetch /api/version in the async settings render — the same unauthenticated endpoint the admin view uses — and render it (blank-safe on fetch failure). Closes #83 Co-Authored-By: Claude Opus 4.8 (1M context) --- frontend/js/views/settings.js | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/frontend/js/views/settings.js b/frontend/js/views/settings.js index 28693c2..9a460f1 100644 --- a/frontend/js/views/settings.js +++ b/frontend/js/views/settings.js @@ -17,6 +17,11 @@ export async function render(container) { // org/workspace membership, gated in the members views, not users.role.) const isAdmin = isSuperAdmin; + // #83: the "About" version was hardcoded (showed v1.4.1 regardless of the build). + // Read it from the server (/api/version) the same way the admin view does. + let appVersion = ''; + try { appVersion = ((await fetch('/api/version').then(r => r.json())).version) || ''; } catch { /* leave blank on failure */ } + container.innerHTML = `
@@ -151,7 +156,7 @@ export async function render(container) {

${t('settings.about')}

-

ScreenTinker v1.4.1

+

ScreenTinker${appVersion ? ` v${esc(appVersion)}` : ''}

${t('settings.about_tagline')}

${t('auth.terms')}