-
v1.7.0
Stablereleased this
2026-07-30 23:45:13 -05:00 | 8 commits to main since this releaseStartup observability — the boot logs now answer "which build is this, what is
it pointed at, and is the LoL monitor actually working?" without shelling into
the container.Added
- Version in the startup logs.
getAppVersion()readspackage.jsonfrom
disk (it sits outside tsconfig'srootDir, and the container's
CMD ["node", "dist/index.js"]means npm never sets
npm_package_version). Reported on the first line of boot, on
Bot startup completed, and in the config summary. - The masked config summary is now actually logged.
Config.getSummary()
existed and masked every secret, but nothing outside tests ever called it — so
a boot revealed almost nothing about its own configuration. It now logs once
per start asStartup configuration. storage.databaseTarget— where the DSN actually points. Host, port,
database, and user parsed out ofDATABASE_URLviadescribeDatabaseUrl().
Deliberately field-by-field rather than a redacted DSN string, so the password
cannot reach a log line through a formatting slip; unparseable values report
parsed: falseinstead of throwing.LoL live monitor configurationline at plugin init. Logs the tracked
queues, poll interval, prediction settings, Riot pacing, and — critically —
riotApiKeyConfigured. Emitted whether the monitor is on or off.
Changed
- A monitor enabled without
RIOT_API_KEYnow warns. That combination wires
no-op API clients that return "no game" forever, which in the logs was
indistinguishable from a healthy monitor whose players simply weren't playing.
Notes
DATABASE_TYPE(logged asdatabaseType) is a free-text label that does not
affect how the bot connects; the newdatabaseTargetis the field that shows
the real destination. Both now appear, with a comment inconfig.tssaying
which is which.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- Version in the startup logs.