v2026.08.29

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: " 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

v2026.08.25.2

Gloom's Build Barn

v2026.08.25.2 (2026-08-25)

Full Changelog Previous Releases

• Docked first open: label widths measured once, and no second chance
  Reported: with GBB docked, the first Talents open draws the panel and the boss
  icons but no text — switch labels, strip header, footer, the dock button's
  caption. Close and reopen and it fills in.
  ⚠️ ONE HALF IS DIAGNOSED, THE OTHER IS NOT, and they are fixed differently.
  DIAGNOSED — the switch labels. makeSwitch sized each label button from
  GetStringWidth() ONCE at build. On a cold open the bundled TTF has not been laid
  out yet and that returns 0, so the button collapsed to 2px and the label, which
  is SetAllPoints to it, had nowhere to draw. Permanent, because the width was
  never revisited.
  The screenshots carry the proof and it is positional, not just missing text: in
  the broken shot both toggle tracks sit ~45px further left than in the working
  one — exactly a collapsed label width, since everything after s.left anchors off
  it. Measuring moved into refresh(), which every Render calls, and a ZERO
  MEASUREMENT IS DISCARDED rather than applied, so a cold frame keeps a placeholder
  and looks approximately right until the real number arrives.
  This predates the icon work — git blame puts it in the original publish commit.
  NOT DIAGNOSED — the strip header, footer and dock caption. Same trigger, no
  confirmed mechanism: they are written by Render()/ApplyDockLayout into a frame
  that on a cold docked open is built, laid out, shown and rendered inside one
  tick while Blizzard_PlayerSpells is still loading. Covered with one deferred
  re-render on show, which is safe because Render() is idempotent — it recomputes
  from state and writes what a warm open would.
  That is a mitigation, not an explanation, and it is labelled as one in the code.
  If it comes back the next report needs evidence, which was impossible to collect:
  GBB.debug was a plain local reset to false every load, so by the time you can
  type /gbb debug the first open has already happened. It now persists in
  SavedVariables, and both the measurement and the deferred render log.

v2026.08.25.1

Gloom's Build Barn

v2026.08.25.1 (2026-08-25)

Full Changelog Previous Releases

• Data refresh: Season 2 only
  Regenerated after pruning talent_builds of content that had left the rotation —
  last season's raid, which WCL still reports as current-expansion and unfrozen,
  and the outgoing M+ dungeons, which the upsert-only write path had never
  removed. 1,120 rows over 18 retired encounters went; 1,040 over 17 remain.
  Payload is now exactly the season: 9 Venomous Abyss bosses, 8 S2 dungeons,
  40 specs, 332 raid slots, 320 M+ slots.
  The diff is small — twelve entries — because most retired encounters had no
  emittable winner and were never reaching the payload anyway. The stale content
  was real but minor; what actually made the addon look un-updated was the
  missing icons in the previous commit.
• Season 2 encounter art, and stop a missing icon being an empty box
  The addon looked un-updated for Season 2. It was not: BuildData.lua had all
  nine Venomous Abyss bosses with good sample counts. What it did not have was
  ART. Encounter icons are bundled per encounter id, all eighteen of them dated
  June, all pre-S2 — so every S2 boss drew an empty square, and the only tiles
  with a picture were the stale Season 1 entries that still had one. That is the
  whole illusion: S2 data wearing S1 icons.
  Adds the seventeen missing icons — nine Venomous Abyss bosses and eight S2
  dungeons — pulled from the same Warcraft Logs CDN the website already renders
  from, keyed by the same WCL encounter id the payload uses, converted to the
  56x56 PNG the existing files use. Three of the dungeons 403 on their zone id
  and needed the site's BOSS_ICON_ID mapping to resolve.
  ⚠️ AND A MISSING ICON MUST NOT BE INVISIBLE. Art is bundled per encounter, so
  the first week of EVERY new tier has data with no picture, and an empty box
  reads as "the addon is broken" rather than "art pending" — which is exactly how
  this was reported. Encounter tiles now fall back to the boss's initials.
  LAYERED, NOT DETECTED. WoW does not reliably report that a texture path failed
  to resolve — a bad path draws nothing and still reads back as set — so the
  fallback sits UNDERNEATH and the real icon covers it when it loads. Bundled
  icons are opaque RGB, so a present icon hides it completely and nothing changes
  for content that has art.
  Initials drop a leading article, because otherwise The Twin Fangs, The Coiled
  Altar and The Lost Explorers all lead with T. Verified across all seventeen S2
  names: every one distinct.

v2026.08.25

Gloom's Build Barn

v2026.08.25 (2026-08-25)

Full Changelog Previous Releases

• Weekly data refresh v2026.08.25

v2026.08.18

Gloom's Build Barn

v2026.08.18 (2026-08-18)

Full Changelog Previous Releases

• Weekly data refresh v2026.08.18

v2026.08.12

Gloom's Build Barn

v2026.08.12 (2026-08-12)

Full Changelog Previous Releases

• Bump Interface to 120100 for patch 12.1
  WoW hides out-of-date addons by default, so the 12.0.7 interface number
  leaves Build Barn missing from the addon list on 12.1. Follows Blizzard's
  XXYYZZ convention (12.0.7 = 120007 -> 12.1.0 = 120100); confirm in-game
  with GetBuildInfo and correct this if the real build differs.
  Not tagged: a release still needs a vYYYY.MM.DD tag, and v2026.08.11 is
  already taken by this morning's automated data refresh.
  Co-Authored-By: Claude Opus 5 noreply@anthropic.com

v2026.08.11

Gloom's Build Barn

v2026.08.11 (2026-08-11)

Full Changelog Previous Releases

• Weekly data refresh v2026.08.11

v2026.08.04

Gloom's Build Barn

v2026.08.04 (2026-08-04)

Full Changelog Previous Releases

• Weekly data refresh v2026.08.04

v2026.07.28

Gloom's Build Barn

v2026.07.28 (2026-07-28)

Full Changelog Previous Releases

• Weekly data refresh v2026.07.28

v2026.07.26

Gloom's Build Barn

v2026.07.26 (2026-07-26)

Full Changelog Previous Releases

• Ship the bundled fonts with their licences
  Khand is SIL OFL 1.1, which requires the licence text to travel with the font
  wherever it is redistributed; OFL.txt now sits beside it. General Sans is
  Indian Type Foundry / Fontshare, whose embedded terms require the fonts to be
  identified by name and ITF's ownership credited - FONT-LICENSES.md does that.
  Both files live in Media/fonts so they are inside the packaged zip.