Description
The Electron auto-updater (electron-updater) attempts to check for updates on every app startup and consistently fails with a 404 because latest.yml is not published at the expected update URL. This generates error logs on every launch.
Log Evidence
From main.log, on multiple dates:
[2026-04-23 ...] error: startup.checkForUpdates.fail { message: 'Cannot find latest.yml at ...' }
The error repeats on each app launch.
Environment
- Version: v0.2 (experimental)
- Platform: Windows 11
Expected Behavior
- For experimental/dev builds without a published update channel, the updater should be disabled or fail silently
- At minimum, this should be a
warn not an error for expected 404s
- The update check should not run if no valid update URL is configured
Impact
- Noisy error logs on every startup
- May confuse users into thinking something is broken
- Wasted startup time waiting for the failed HTTP request
Notes
Related to #124 (test vs generate path mismatch) — the "test connection shows timeout but actually works" behavior may be partially caused by this same update-check latency adding to perceived startup slowness.
Description
The Electron auto-updater (
electron-updater) attempts to check for updates on every app startup and consistently fails with a 404 becauselatest.ymlis not published at the expected update URL. This generates error logs on every launch.Log Evidence
From
main.log, on multiple dates:The error repeats on each app launch.
Environment
Expected Behavior
warnnot anerrorfor expected 404sImpact
Notes
Related to #124 (test vs generate path mismatch) — the "test connection shows timeout but actually works" behavior may be partially caused by this same update-check latency adding to perceived startup slowness.