[Bug]: UI is now showing multiple instances of the Maintainer cut pre-release

[prom3theu5]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

Nightly: 0.0.41-nightly.20260914.1700

MacOS Desktop is pulling in change log feed from the maintainer cut versions - and the release notes show it multiple times?

As far as I know this was previously filtered out so an in app upgrade what not install the maintainer cut release?
(Which im guessing has things like orchestrator 2 or other things which would be a broken migration of local db?)

Expected behavior

Show upgrades related to release track you are on, and not offer possible breaking

Actual behavior

Shows the release track with maintainer releases - i am not going to click upgrade on it just in case lol

Impact

Blocks work completely

Version or commit

0.0.41-nightly.20260914.1700

Environment

MacOS

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

[juliusmarminge]

Thanks for the report — this looks like a real nightly changelog leak, not a duplicate of #11584 / #4374 / #11708.

What’s going on

Nightly desktop enables electron-updater fullChangelog (apps/desktop/src/updates/DesktopUpdates.ts) and then renders whatever normalizeDesktopUpdateReleaseNotes() keeps (apps/desktop/src/updates/releaseNotes.ts → SidebarUpdateReleaseNotes). That normalizer has no channel / preview filter.

electron-updater ^6.6.2 builds the full changelog from GitHub releases.atom as “every semver greater than the running version,” then sorts with semver.rcompare. It does not stay on the nightly track.

Because preview > nightly as a semver prerelease id, every 0.0.41-preview.* maintainer-cut release compares newer than a 0.0.41-nightly.* install and sorts to the top of the popover. There are several of those on the feed right now (T3 Code Preview (maintainer test build, do not install) …), which matches “the maintainer cut shows up multiple times.”

That is separate from GitHub’s own generated nightly notes, which already compare tag-to-tag within the same channel.

Will Upgrade install preview?

Very likely no. GitHubProvider still picks the newest tag whose prerelease id is nightly, then downloads that tag’s nightly*.yml. Preview releases are published without updater manifests (isDesktopPreviewVersion in scripts/build-desktop-artifact.ts), and handleUpdateAvailable ignores a version whose resolved channel is not the one you’re on (preview maps to "latest", not "nightly").

So the offered availableVersion should still be a nightly (for 0.0.41-nightly.20260914.1700, that would be 0.0.41-nightly.20260914.1707 at the time of this note). The popover is just showing preview notes first, which makes the CTA look unsafe.

Not covered by existing work

#11584 is a history UI request. #11583 only groups feat/fix/chore. #8976 is custom update sources. Recent preview-train commits kept preview off updater files / npm, not off this Atom changelog.

Next step

Filter -preview. (and any non-nightly prerelease) out of normalizeDesktopUpdateReleaseNotes on the nightly channel before the 6-group cap, and add a mixed nightly+preview test. Until that lands, refusing the button is understandable, but it should not be required to avoid a preview / broken-migration install.

Accepting as a desktop updater UI bug.

[prom3theu5]

Sorted now - thanks for fast turn around