Skip to content

feat(updater): "Pre-Release" label above the update banner - #76

Merged
Nic-dorman merged 1 commit into
mainfrom
feat/update-banner-prerelease-label
May 1, 2026
Merged

feat(updater): "Pre-Release" label above the update banner#76
Nic-dorman merged 1 commit into
mainfrom
feat/update-banner-prerelease-label

Conversation

@Nic-dorman

Copy link
Copy Markdown
Contributor

Summary

Adds a small "Pre-Release" header line above the existing teal "Update Available" banner so testers can see the channel of the offered update at a glance, not just from the version string.

Visual

When the offered update is a pre-release (isPrerelease === true), the sidebar banner stacks three lines:

PRE-RELEASE        ← new (text-[10px], uppercase, bold, opacity-70)
UPDATE AVAILABLE   ← existing (text-xs, uppercase, bold)
v0.6.8-rc.X        ← existing (text-xs, opacity-80)

Stable update banners are unchanged — no extra label, amber palette as before.

Pairs with

Test plan

  • npx nuxi build clean
  • Manual on Windows dev with faked v0.6.6 + pre-release toggle on → banner shows the three-line stack with "Pre-Release / Update Available / v0.6.8-rc.2".
  • CI green
  • Reviewer: confirm spacing / weight reads cleanly. The new line uses text-[10px] and opacity-70 to give the existing "Update Available" headline visual primacy — easy to bump up if the hierarchy feels wrong.

When the offered update is a pre-release, the teal sidebar banner now
shows three lines:

    PRE-RELEASE
    UPDATE AVAILABLE
    v0.6.8-rc.X

The new label is text-[10px] uppercase bold with reduced opacity so the
existing "Update Available" headline keeps visual primacy. Stable
updates render unchanged (no extra label, amber palette).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Nic-dorman
Nic-dorman merged commit 213ecec into main May 1, 2026
4 checks passed
@Nic-dorman
Nic-dorman deleted the feat/update-banner-prerelease-label branch May 1, 2026 09:10
Nic-dorman added a commit that referenced this pull request May 1, 2026
Fourth internal-tester pre-release. Adds on top of rc.3:
- "Pre-Release" header line above the teal "Update Available" banner
  (#76) -- testers see the channel of the offered update at a glance
  without having to parse the version string.

Cut quickly after rc.3 so testers on rc.1/rc.2 (Linux/macOS) can
exercise the V2-237 + #73 install path twice: once upgrading to rc.3,
then again from rc.3 to rc.4 (verifies the fix is sticky across
multiple upgrade cycles).

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant