• v1.13.1 48cf31b731

    v1.13.1 — stop restart recovery discarding a live game
    All checks were successful
    CI / build-and-test (push) Successful in 1m45s
    CI / docker-build (push) Successful in 25s
    Stable

    joeyr released this 2026-08-25 20:47:05 -05:00 | 66 commits to main since this release

    Fixed

    • Restart recovery discarded a live game every time the bot restarted.
      activeGameTracker persists the platformId that came back on spectator data
      (NA1), but getPlatform accepted only user-facing region codes (NA) and
      threw Unknown region: NA1. recoverActiveGames caught the throw, marked the
      game stale and cleaned it up, so a genuinely in-progress game lost its
      end-of-game notification on every deploy — observed twice in ten minutes
      across the 1.13.0 rollout (games 5628417643 and 5628441631). getPlatform now
      accepts either form, matching getRoutingFromRegionOrPlatform, which had
      handled both all along. Unrecognised values still throw, so a typo fails
      loudly rather than reaching Riot as a malformed hostname.

    Changed

    • .env.config drops LOL_RIOT_MAX_REQUESTS_PER_2MIN from 75 to 40, so the
      repo's mirror agrees with the code default 1.13.0 introduced. The deployed
      stack pins these same three variables, which is why the 1.13.0 rollout came up
      still reporting riotMaxPer2Min=75 — the image had changed but the
      environment overrode it. The comment now says outright that leaving them unset
      is preferred, since pinning a copy of the default is what made the default
      dead config.
    Downloads