Spectralis devlog #11
—Hello again proggers—
Docs got a full rework this round. Also turns out v5.4.1 went out to nobody, because it never actually got pushed to the CDN. Tagged, released, announced probably, and completely inaccessible the whole time.
shipped a release into a void and called it done
Cat or dog? docs/
Okay let’s get into it~
—Yap—
Started as a documentation pass and ended with the realization that the last release had been sitting local this whole time instead of where anyone could actually get it. Two very different kinds of work, same devlog.
—The Great Suffering—
1 — The Entire Doc Rework
Not a touch-up, a full rework. Docs, README, and STANDARDS all got restructured rather than patched in place, since patching them individually over the last several devlogs had left them internally inconsistent with each other and with what the app actually does now.
2 — 5.4.1 Never Made It To The CDN
The actual headline bug of this devlog. v5.4.1 shipped, in the sense that it was built, tagged, and probably announced somewhere — but never got pushed to the CDN, meaning nobody could actually download it. Public-facing, and it was quietly broken the whole time until someone noticed.
a release that ships to nowhere didn’t really ship
3 — Fixed And Actually Pushed
Corrected the CDN push so 5.4.1 is genuinely available now, not just tagged in git looking like it is. Also part of why the doc rework mattered — docs referencing a version nobody could download was its own kind of lie.
—FAQ (no one asked these but they are here)—
Q: What is a “progger”?
A: A human programmer. You. The one who tagged a release and forgot the part where people can actually get it.
Q: How long was 5.4.1 unavailable?
A: Long enough to be embarrassing, short enough to fix before it became a real problem. Caught during this pass.
Q: Why redo the docs entirely instead of patching them again?
A: Because incremental doc patches across several devlogs had drifted apart from each other and from the app. A full rework got everything back in sync at once.
Q: Is this the same CDN that serves changelogs now (devlog #5)?
A: Same one. This time the release binary itself was the thing missing, not just content.
Q: Anything else quietly broken that hasn’t surfaced yet?
A: Unknown by definition. That’s what the next devlog is for.
—This is the end*—
*end for now, CDN pushes permitting
POPPY!!!