watn3y/steamsalty
Watch
1
0
Fork
You've already forked steamsalty
 0
Code Issues 1 Pull requests 2 Projects Releases 3 Packages 1 Wiki Activity Actions
3 releases 3 tags
  • v2.0.1 4bf40b9fe7

    Version 2.0.1 Stable

    watn3y released this 2026-10-15 07:10:11 +02:00 | 3 commits to master since this release

    Signed by watn3y
    SSH key fingerprint: SHA256:W1qdFUDGjmkp+0oY9axqbTj9/4dBCIZ4veq5ZFqKSlU

    Fixes

    • Use the correct Go version for docker builds

    Full Changelog: https://git.watn3y.de/watn3y/steamsalty/compare/v2.0.0...v2.0.1

    Downloads
  • v2.0.0 d6bc3e2cf6

    Version 2.0.0 Stable

    watn3y released this 2026-10-15 06:51:01 +02:00 | 5 commits to master since this release

    Signed by watn3y
    SSH key fingerprint: SHA256:W1qdFUDGjmkp+0oY9axqbTj9/4dBCIZ4veq5ZFqKSlU

    Breaking changes

    All environment variables use the new pattern STEAMSALTY_<SERVICE>_<SETTING>. The old names are no longer used.

    v1.0.0 v2.0.0
    STEAMSALTY_CHATID STEAMSALTY_TELEGRAM_CHATID
    STEAMSALTY_STEAMAPIKEY STEAMSALTY_STEAM_APIKEY
    STEAMSALTY_WATCHERS STEAMSALTY_STEAM_WATCHEDPROFILES
    STEAMSALTY_SLEEPINTERVAL STEAMSALTY_STEAM_SLEEPINTERVAL
    STEAMSALTY_TRANSLATE_ENABLED STEAMSALTY_DEEPL_ENABLED
    STEAMSALTY_TRANSLATE_LANGUAGE STEAMSALTY_DEEPL_TARGETLANGUAGE

    STEAMSALTY_LOGLEVEL, STEAMSALTY_TELEGRAM_APITOKEN, STEAMSALTY_DEEPL_APIKEY and STEAMSALTY_DEEPL_FREETIER are unchanged.

    Caution

    Make sure to update your environment variables before upgrading to v2.0.0

    Notable changes

    • Notifications work again. Steam changed the HTML of its comment section so some changes were needed to fix how SteamSatly parses the profiles.
    • A setting of STEAMSALTY_STEAM_SLEEPINTERVAL must now be least 1. If the value is 0 or less SteamSatly exits at startup.
    • Required variables can no longer be empty. An empty STEAMSALTY_TELEGRAM_CHATID= used to start the bot with ChatID 0. Now it fails with "missing required value".

    Fixes

    • No more crashes when Steam misbehaves. Errors from the Steam API and network errors crashed SteamSalty, both in the watchers and in /info. They are now logged instead.
    • Comments are no longer lost during Steam outages. Steam error pages (such as 502 or 503) were treated like an empty comment section, which made SteamSalty skip comments posted around that time. Failed requests are now retried.
    • Fallbacks when Steam data is unavailable. If a profile name can't be loaded, notifications and /info show the SteamID instead. When /info can't reach Steam, it shows "unknown" instead of "never" and 0 comments.
    • Comments containing <, > or & are delivered. Previously these characters weren't escaped, which could make Telegram reject the notification.
    • No more "Translated from" block when the translation is identical to the original text.
    • Fetching comments times out after 30 seconds, so a stalled connection can no longer freeze a watcher.
    • The Steam API key no longer appears in the log when a Steam API request fails due to a network error.

    Other changes

    • README: environment variables are now grouped by service.
    • Updated the Docker image's OCI labels.
    • Added unit tests (go test ./...).

    Full Changelog: https://git.watn3y.de/watn3y/steamsalty/compare/v1.0.0...v2.0.0

    Downloads
  • v1.0.0 f720d4482b

    Version 1.0.0 Stable

    watn3y released this 2026-05-05 01:16:12 +02:00 | 20 commits to master since this release

    Signed by watn3y
    GPG key ID: 179C0B15B70581C4
    Downloads