Loot Advisor

v2026.08.29-1626 (2026-08-29)

Full Changelog Previous Releases

• The weekly data refresh never published to CurseForge
  It had NO CurseForge token at all, and carried GITHUB_OAUTH on the step rather
  than the job. The packager treats a missing token as "do not publish there" -
  no error, exit 0 - so today's data release went to GitHub and skipped CurseForge
  in silence. Exactly the failure that cost two days in Session 253, which was
  fixed in release.yml and never here.
  Left alone this was worse than a one-off: CurseForge would have received the
  addon's CODE on every tag and its DATA never, so the season's loot table would
  have frozen there at whatever shipped first while GitHub users updated weekly.
  Job-level env, both token names from the one secret, and the same plain-words
  credential check release.yml carries - because the only honest signal is a line
  saying the token arrived.