sassanix/Warracker 1.0.6

on GitHub

⚙️ Release 1.0.6 – Docker Startup Fix & Total Value Formatting

Version 1.0.6 is a hotfix for 1.0.5. The 1.0.5 Docker image fails to start on a clean install, and this release fixes that. It also fixes the status dashboard's Total Value card, which ignored the currency position setting and formatted its amount by hand. Nothing else changes.

🐳 Docker

• Image fails to start, fixed (#293, reported by firatkupeli): the 1.0.5 image crashes on boot with ModuleNotFoundError: No module named 'packaging', gunicorn never starts, and the API returns 502 while the frontend loads. The cause: gunicorn loads its gevent worker class at startup, that class imports the packaging module, but gunicorn declares packaging only in its optional "gevent" extra, and the requirements file installs plain gunicorn, so pip never installed it. The 1.0.4 image worked because it copied the builder's whole Python installation, which happened to carry packaging along; the smaller 1.0.5 image copies only the virtualenv, which exposed the missing pin. packaging is now pinned explicitly in the requirements file, and a regression test guards the pin so it cannot be pruned as unused. If you rolled back to 1.0.4, it is safe to update again.

💱 Dashboard

• Total Value formatting, fixed (#294, reported by nesha14586): the Total Value card on the status dashboard formatted its amount by hand, with the currency symbol hardcoded in front, no spacing, and no thousands separators, ignoring the currency position setting. A user with Serbian Dinar and the symbol set to appear after the amount saw дин182591.00 on the dashboard while their warranty entries correctly showed 52790.00 дин. The card now uses the same shared currency formatter as the warranty cards, honoring the position setting and the symbol spacing, and the shared formatter now adds locale thousands grouping everywhere, so the total reads 182,591.00 дин. The card also no longer forces the value onto one line, so large totals wrap inside the card instead of overflowing it.

Upgrading: back up (database + uploads volume), pull the new image, recreate the container. No migrations need manual steps. One carried-over note on database credentials (#221): DB_USER, DB_PASSWORD, DB_ADMIN_USER, and DB_ADMIN_PASSWORD should be set explicitly. The built-in defaults still work in 1.0.6 and startup logs a deprecation warning naming any of the four that are not set; the defaults will now be removed in 1.0.7, not 1.0.6 as originally announced, because this hotfix took the 1.0.6 slot. Both shipped compose files and the Unraid template already set all four.