0.9.27 doesn't find update to 0.9.29 #104

New Issue

Nerdinat0r · 2026-07-29T10:50:35+02:00

Nerdinat0r commented

2026-07-29 10:50:35 +02:00

Description

Steps to Reproduce

have 0.9.27 installed
click on settings -> check for updates

Expected Behavior

finds and installs 0.9.29

Actual Behavior

"no stable releases found"

Environment

KX-Bridge Version: 0.9.27
OrcaSlicer Version: orcaslicer-kx 2.4.2
Moonraker/Klipper Version:
Operating System: Linux
Installation: Docker

Logs

<!-- docker logs kx-bridge --tail 50 -->

## Description  ## Steps to Reproduce 1. have 0.9.27 installed 2. click on settings -> check for updates ## Expected Behavior finds and installs 0.9.29 ## Actual Behavior "no stable releases found" ## Environment - KX-Bridge Version: 0.9.27 - OrcaSlicer Version: orcaslicer-kx 2.4.2 - Moonraker/Klipper Version: - Operating System: Linux - Installation: Docker ## Logs ```  ```

Nerdinat0r added the

bug

label 2026-07-29 10:50:35 +02:00

Nerdinat0r commented

2026-07-29 12:31:51 +02:00

Using "docker compose pull && docker compose up -d" does install the update.
Its just the GUI that won't find it.

Using "docker compose pull && docker compose up -d" does install the update. Its just the GUI that won't find it.

viewit commented

2026-08-02 14:18:49 +02:00

Thanks for confirming the Docker Compose path works, @Nerdinat0r — that pointed me straight at the actual bug.

Root cause: the in-app update check for stable releases only requested the single newest release from Gitea (limit=1), regardless of type. Nightly/dev prereleases publish far more often than stable releases, so that single newest release is almost always a nightly prerelease — the check then filters for "not a prerelease" and finds nothing, even though a newer stable release (0.9.29) exists further back in the release list. docker compose pull works because it just pulls the :latest tag directly, bypassing this broken check entirely.

Fixed by requesting enough releases to look past a run of prereleases and find the actual latest stable one. Committed on nightly, will go out with the next nightly build (and of course the next stable release itself).

Thanks for confirming the Docker Compose path works, @Nerdinat0r — that pointed me straight at the actual bug. **Root cause:** the in-app update check for stable releases only requested the single newest release from Gitea (`limit=1`), regardless of type. Nightly/dev prereleases publish far more often than stable releases, so that single newest release is almost always a nightly prerelease — the check then filters for "not a prerelease" and finds nothing, even though a newer stable release (0.9.29) exists further back in the release list. `docker compose pull` works because it just pulls the `:latest` tag directly, bypassing this broken check entirely. Fixed by requesting enough releases to look past a run of prereleases and find the actual latest stable one. Committed on `nightly`, will go out with the next nightly build (and of course the next stable release itself).

viewit closed this issue

2026-08-02 14:22:44 +02:00

viewit referenced this issue from a commit

2026-08-02 16:30:44 +02:00

feat(printer): add smart-plug power switch button (Issue #103); fix(update): stable update check missing behind prereleases (Issue #104)

Sign in to join this conversation.

Branches Tags

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: viewit/KX-Bridge-Release#104