Closed bug report

In-app updater says 0.1.419 is current; public version.json was never promoted to 0.1.420

Drew Owens · 15d ago ·closed by Kyle Bergstedt

What happens: Settings → Updater → Check now said "No updates found. You are on 0.1.419." But the wiki page shows Latest: v0.1.420, published 2026-10-20, with a 0.1.420 DMG on the download card. The in-app updater never offered 0.1.420, so the user had to download and install it by hand from the wiki.

Cause (confirmed): The public manifest the updater polls, version.json on this page, still says 0.1.419. The release registry and the page's download card say 0.1.420.

  • adom-wiki repo show adom/hydrogen-macos version.json → "version": "0.1.419", released_at 2026-10-20T20:08:37Z
  • The last manifest commit is promote hydrogen-macos 0.1.419 to public (Kyle, 2026-10-20).
  • Release 0.1.420 was published at 2026-10-20 20:42, about 34 minutes later, but was never promoted into version.json.
  • 0.1.419 has a DMG at /download/.../0.1.419/ (HTTP 200) but no entry in the release list. So the release list jumps 0.1.418 → 0.1.420, and the manifest is on a version that the page doesn't list.

Live updater state, now that the user has installed 0.1.420 by hand (GET /updater/status on the Hydrogen control API):

current_version 0.1.420   latest_version 0.1.419   update_available false
channel stable  tier public  flavor public  last_check_at 2026-10-26T18:21Z  last_check_error null

So a week later, every public Mac user on 0.1.419 or earlier is still being told they're current.

Side note: /buildinfo on the installed 0.1.420 reports build_sha 5870c313…-dirty (built Oct 20 3:39 PM). The 0.1.420 release record lists commit_hash 8a8a6a5f…. So the shipped build doesn't match the recorded commit, and it was built from a dirty tree.

Expected / asks

  1. Promote 0.1.420 to the public version.json, or whichever version is meant to be current, so the release list, the download card and the manifest agree.
  2. Make publish and promote one step, or make publish refuse to finish while the public manifest is behind the newest public release. The Windows scripts already read the manifest back after publishing (see #3).
  3. Add a 0.1.419 release entry or retire it, so the manifest never points at a version the page doesn't list.

Environment: Hydrogen for macOS, Apple Silicon. It was 0.1.419 when the bug showed up; it's now 0.1.420, installed by hand.

Reported by Drew (drew715). @kyle FYI, this is a macOS release pipeline issue.

4

5

1 Reply

Kyle Bergstedt closed this · 4d ago
Kyle Bergstedt reopened this · 4d ago
Kyle Bergstedt · 4d ago

fixed: insiders builds live on the private dev page and promote is the only way to public, so the release list and version.json move together. 0.1.429-dev.12 makes release builds refuse a dirty tree

Kyle Bergstedt closed this · 4d ago

Log in to reply.