Gloom's Build Barn

v2026.08.29 (2026-08-28)

Full Changelog Previous Releases

• Point the packager at CurseForge project 1671911
  Pairs with the CF_API_TOKEN repo secret, already set. The CurseForge token is
  per ACCOUNT, so the one secret serves this addon and the Loot Advisor (project
  1671489). With the id present, both release.yml and the Tuesday weekly-data.yml
  now publish to GitHub AND CurseForge in one run.
  Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
• Wire both release workflows for CurseForge
  WoWUp's GitHub provider is broken for UPDATES -- it fetches the API asset URL
  without the octet-stream header and unzips GitHub's JSON metadata (WowUp.CF
  issues #103 and #107, open since February with the fix written but unshipped).
  Installing works, updating does not, and the only per-user workaround is a
  GitHub personal access token, which is not something to ask of raiders. This
  addon has shipped from GitHub Releases since June; that path is now a
  non-starter for anyone but its author.
  ⚠️ BOTH WORKFLOWS, because weekly-data.yml is the one that actually ships most
  releases -- it self-packages every Tuesday rather than relying on the tag push,
  since tags pushed by GITHUB_TOKEN do not trigger other workflows. Wiring only
  release.yml would have left the weekly release publishing to GitHub alone.
  ⚠️ ENV AT JOB LEVEL, per the packager's own documented example. It is a
  COMPOSITE action and step-level env reaching its inner steps is unreliable:
  the Loot Advisor's first CurseForge upload was silently lost to exactly that,
  printing "CurseForge ID: <id>" with no "[token set]" beside it while GitHub's
  token on the same step worked. Both CF_API_KEY and CF_API_TOKEN are set from
  the one secret -- release.sh checks the former first and the documented example
  uses it.
  A MISSING TOKEN IS SILENT BY DESIGN: the packager treats it as "do not publish
  there" and exits 0, so a release that uploaded nowhere looks exactly like one
  that worked. Each workflow now states whether each credential arrived, without
  printing any of them. The silence was the real defect.
  STILL NEEDED: a CurseForge project for this addon and its numeric id on the
  .toc. The CF_API_TOKEN secret is already set -- the CurseForge token is per
  ACCOUNT, so the same one serves both addons.
  Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com