Small UI bug in update notification

[vedpawar2254]

Where did this happen?

Desktop app (macOS)

Version

1.15.0

What happened?

Steps to reproduce

1. see the sidebar at bottom left

Logs, screenshots, or recordings

No response

[github-actions]

I could not view the image attached to the issue (the comment body only gives me its dimensions, 228×81 — consistent with a crop of the sidebar footer cluster), so this is a code-level triage of the component that owns that spot rather than a confirmation of the specific glitch.

What's on screen there

The bottom-left "update notification" is UpdatesPill, mounted in the sidebar footer next to the org dropdown and the gear:

• apps/desktop/src/renderer/components/UpdatesPill/UpdatesPill.tsx
• Mounted at apps/desktop/src/renderer/routes/_authenticated/_dashboard/components/DashboardSidebar/DashboardSidebar.tsx:320 (dashboard sidebar) and apps/desktop/src/renderer/screens/main/components/WorkspaceSidebar/WorkspaceSidebarFooter.tsx:95,177 (workspace sidebar)
• Status comes from the main process: apps/desktop/src/main/lib/auto-updater.ts → apps/desktop/src/lib/trpc/routers/auto-update/index.ts → useAutoUpdateStatus.ts

It renders five visually distinct things, and which one you saw determines which suspect below applies: download ring + NN%, braille spinner + [·##···] while installing, green dot + ↑ update when ready, green check + v<version> for ~5s after relaunch, red dot + ↻ retry on failure.

Suspects, ranked

1. Version string looks truncated in the post-update ✓ pill — UpdatesPill.tsx:43-46, rendered at :279:

function displayVersion(version: string): string {
	const [base, prereleaseTag] = version.split("-", 2);
	return prereleaseTag ? `${base}-${prereleaseTag.slice(0, 2)}` : base;
}

Any prerelease suffix is clipped to two characters, so a canary build renders as ✓ v1.15.1-ca. It's deliberate (the comment explains it's to avoid overflowing the footer), but in a screenshot it reads exactly like a text-truncation bug. If your build is a canary, this is almost certainly what you photographed.

2. Same pill falls back to the word "downloaded" — UpdatesPill.tsx:279: when version is missing, the post-update confirmation shows a green check next to downloaded, which is the wrong word for that state ("updated"). The main process always passes a version at auto-updater.ts:430, so this should only be reachable via the dev-mode install path (auto-updater.ts:155-157 reuses currentVersion, which can be undefined).

3. Countdown border doesn't match the pill's corners in the collapsed sidebar — UpdatesPill.tsx:187 passes radius={5} for a button styled rounded-md. The theme sets --radius: 0.625rem (apps/desktop/src/renderer/globals.css:45), so --radius-md is 8px; allowing for the 0.75px stroke inset the traced rect should be ≈7.25px, not 5. The result is a visibly squarer traced outline than the button it's tracing, for the 5s the confirmation is up. In the expanded pill the radius is measured instead (CountdownBorder.tsx:31-34), so this one is collapsed-sidebar-only.

4. Measured radius can degrade to a square trace — CountdownBorder.tsx:33 computes (svgRef.current.clientHeight - STROKE_WIDTH) / 2 once, in a layout effect keyed only on radius. If that measurement ever comes back 0, rx becomes -0.75 (invalid, ignored) and the countdown line traces a sharp-cornered rectangle over a rounded-full pill. It also never re-measures if the pill's height changes.

5. Footer gets cramped when the pill appears — DashboardSidebar.tsx:305-318: the row is flex items-center gap-1 p-2 with the org dropdown in min-w-0 flex-1 and the pill shrink-0 (UpdatesPill.tsx:222). The ↑ update pill is ~75px wide, so the org name truncates the moment an update becomes available, and the ~20px-tall pill sits between two 32px controls.

What I ruled out: the update state machine itself looks sound — emitStatus replays current status to new subscribers (auto-update/index.ts:20), and the install/retry click paths are guarded (UpdatesPill.tsx:142-153, auto-updater.ts:167-178).

Reproducing

Each state can be forced without waiting for a real release — in a dev build, either the Debug menu (apps/desktop/src/main/lib/menu.ts:176-187: "Simulate Update Downloading / Ready / Error") or the command palette (commands.tsx:183-211: Simulate update: downloading | ready | error). For the ✓ confirmation specifically: simulate ready, click the pill — dev-mode installUpdate() fakes the lifecycle and emits UPDATED after 3.5s (auto-updater.ts:150-161). Toggle the sidebar collapsed/expanded to hit suspects 3 and 5.

For suspects 1 and 2 a unit test is enough, once displayVersion is exported from UpdatesPill.tsx:

import { expect, test } from "bun:test";
import { displayVersion } from "./UpdatesPill";

test("keeps prerelease versions readable", () => {
	expect(displayVersion("1.15.0")).toBe("1.15.0");
	expect(displayVersion("1.15.1-canary.20260711221936")).toBe("1.15.1-canary"); // currently "1.15.1-ca"
});

Fix direction

For 1, reuse the existing tooltipVersion logic (UpdatesPill.tsx:49-52) for the pill too — it drops the canary timestamp but keeps the whole tag (1.15.1-canary) — and let the pill truncate with CSS if it's too wide, rather than mid-word slicing. For 3, derive the traced radius from the theme token (calc(var(--radius-md) - 0.75px)) instead of the hard-coded 5. For 4, re-measure via ResizeObserver and skip rendering the rect when the measured height is 0 rather than emitting a negative rx.

To narrow this down definitively: could you say which of the five states was on screen (green ↑ update, green ✓ with a version, red ↻ retry, a percentage, or the spinner), whether the sidebar was expanded or collapsed, and whether you're on the stable or canary channel?

[andyst-dev]

This was fixed on 2026-07-25 in commit 263db56 ('let the v1 add-repository button shrink so the settings gear isn't clipped') — the add-repository trigger gained min-w-0 flex-1 shrink with a truncated label, so the footer's '↑ update' pill and settings gear are no longer pushed past the sidebar edge or clipped. The reporter was on 1.15.0 (release 2026-07-13); the fix landed ~12 days later and is in current main (1.20.x). Closing as resolved — please reopen if it still reproduces on a recent build.

[andyst-dev]

This was fixed on 2026-07-25 in commit 263db56 ('let the v1 add-repository button shrink so the settings gear isn't clipped') — the add-repository trigger gained min-w-0 flex-1 shrink with a truncated label, so the footer's '↑ update' pill and settings gear are no longer pushed past the sidebar edge or clipped. The reporter was on 1.15.0 (release 2026-07-13); the fix landed ~12 days later and is in current main (1.20.x). Resolved — please reopen if it still reproduces on a recent build.