Skip to content

fork nightlies never update on the nightly channel [📡#1388] #1389

Description

@donjor-agent

🤖 claude/anthropic claude-opus-5-5 (high)

A fork nightly on the nightly channel never offers the next nightly.

Origin: UAT walk of c8b021a205 on 2026-09-28, packaged .775 AppImage against a mock feed offering .776.

Steps

  1. Install v0.0.43-hyprws-nightly.20260928.775
  2. Fresh settings: channel is latest ❌
  3. Switch to nightly, Check for Updates
  4. Feed offers 0.0.43-hyprws-nightly.20260928.776
  5. Log: "ignoring update that does not match…" ❌
  6. App reports up to date ❌

The title bar and tab read "T3 Code (Alpha)", not Nightly.

Cause

apps/desktop/src/updates/updateChannels.ts matches nightlies with /^[^-+]+-nightly\.\d{8}\.\d+$/.
0.0.43-hyprws-nightly.… never matches, so every fork nightly classifies as latest.

Consumer Effect
DesktopUpdates.ts applyUpdateAvailable drops every fork nightly
DesktopAppSettings.ts default channel latest on a nightly build
DesktopEnvironment.ts stage label "Alpha", not "Nightly"
releaseNotes.ts drops fork nightly notes

#763 fixed the updater feed channel; this guard sits after it, so the live acceptance box on #762 still fails.
The fork touches these files: run upstream-triage before fixing.

Close conditions

  • Match: -hyprws-nightly. is nightly
  • Update: .775 on nightly accepts .776
  • Default: fresh fork nightly picks nightly
  • Branding: stage label reads Nightly
  • Stable: -hyprws.N stays latest
  • Test: fork versions pinned

Relates to #762.

Activity

  1. added a commit that references this issue on Sep 29, 2026
    67ab6f9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    releasepublishing, versioning, rollout

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions