Repository navigation
Summary
Security and reliability patch release 0.5.4 for the supported 0.5 stable line. All 0.5.3 users should upgrade.
Security
- Passwords that start with
-are masked too. A value such as--password=-…,--password -…,redis-cli -a -…orsshpass -p -…used to stay visible in container and image details, including container errors. It is now masked. A neighbouring option after a password flag (-h db,--verbose,-) stays readable. - The state folder is private from the start. The official Compose file and the docs give the
/run/pytmbottmpfsmode=0700. The bot already locked the folder down on its first write; this closes the short window before that.
Reliability
- Resource alerts are no longer lost. If Telegram didn't accept a CPU, memory, disk or temperature alert (network error, notification limit reached), the bot stayed silent until the value returned to normal. Now the alert is sent again on the next check, with the same Event ID, until it gets through. A "has normalized" message is sent only for an alert you actually received.
- Clear logs while Telegram is down. For each alert the log shows, once and with its Event ID, when delivery broke and when it recovered (or that the value normalized first). It no longer repeats the same error on every check.
--check-dockertells the truth. It used to check only the socket file permissions and said "OK" even when Docker didn't answer. Now it exits with0only if Docker responds. It uses the Docker settings frompytmbot.yamlwhen the file is mounted, and the standard local socket otherwise.
Upgrade notes
- Docker: pull
orenlab/pytmbot:0.5.4, or0.5/stableonce the release workflow has finished, and recreate the container. - Config version: set
config_version: "0.5.4"to match the running app version.0.5.3configs still load, and auto-migration handles the mismatch on startup. - Compose file: if you copied it earlier, add
mode=0700to the/run/pytmbottmpfs line. --check-dockerin scripts: it now exits with1when Docker doesn't answer, even if the socket is accessible (for example, a wrong host in the config).- End of life:
0.5.3is end-of-life as of this release.
Full Changelog: v0.5.3...v0.5.4