Update check finds dev release instead of stable; version not updated after update #14
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Reported by: u/Nerdinat0r (Reddit)
Bug 1 – Update check offers dev release to stable users
When checking for updates on a stable install (0.9.1-beta15), the bridge finds the latest dev pre-release instead of v0.9.2.
Root cause:
STABLE_RELEASE_APIhaspre-release=truein the query parameter, which returns only pre-releases.Bug 2 – Version not updated after self-update
After installing an update via the Web-UI, the displayed version still shows the old version after restart.
Root cause: The update only downloads
kobrax_moonraker_bridge.py, but not theVERSIONfile. The oldVERSIONfile remains on disk.Bug 3 – VERSION file missing from Docker image
On a fresh install from the v0.9.2 release, the
VERSIONfile is not included in the Docker image (COPY VERSION .missing from Dockerfile)._read_version()returns"unknown".Feature request – Show running version in GUI
It would be helpful to see the currently running version directly in the UI header without opening the Settings menu.
All four issues will be fixed in the next release.
Fixed in v0.9.3 (upcoming).
Bug 1 – Update check:
STABLE_RELEASE_APIhadpre-release=truewhich caused stable users to receive dev builds. Fixed — stable users now only see stable releases.Bug 2 – Version not updated: The
VERSIONfile was missing from the Docker image (COPY VERSION .was absent from the Dockerfile). Since_write_version()only writes when the file already exists, the version was never updated. Fixed in Dockerfile.Bug 3 / Feature – Version in GUI: Running version is now shown in the Web-UI header next to the printer name. No need to open Settings to check which version is running.
Thank you for the detailed report!