The beta track moved to 1.60.1.70291 on October 8 at 20:27 UTC, up from 70245.
Single push, new binary
| Sequence | Time (UTC) | Build | build_config |
|---|---|---|---|
| 4066960 | Oct 8, 20:27 | 1.60.1.70291 | e8dd824c |
| 4063876 | Oct 7, 18:53 | 1.60.1.70245 | 0bf14126 |
One sequence, one config change. Genuinely new build, not a re-point. Product config and keyring stable, regions in parity.
The coincidence, stated carefully
Kaivax's development notes, new Dalaran dungeon, 16 free Legacy points, dungeon XP increase, landed the same day. The notes name no build number.
It would be easy to write that 70291 contains the Dalaran dungeon. That is plausible and unverified: the notes could equally describe server-side content independent of any client, and the manifest says nothing about dungeons either way. So this post records the coincidence with the date shared and stops there.
If a fan diff later compares 70291 against 70245 record by record, that comparison will settle it. Until then the honest position is two facts side by side.
Fan coverage lags one build
Neither reference that diffs builds has published 70291 yet. Their latest remains the 70245-versus-70235 comparison at zero changes. The gap between our manifest reading and their written record, which closed briefly this week, is open again by one build.
SOURCES: the wow_classic_beta manifest and seqn history via the blizztrack API, read October 9 2026. Version, timestamp and config values transcribed. The Kaivax notes timing is from the mirrored blue posts dated October 8. Related: the Dalaran notes, the two-track fix, and what our build reports mean.