nextDash 1.3.3 rebuilds the page you land on. The overview used to answer “what is new?” in different places at once, none of them well, while the news from the project itself sat below the fold on most screens. It is one list now, newest first. The form for adding a bookmark got the same treatment for the same reason — it had grown taller than a laptop screen, so the Save button was out of sight on the machine most people use. Behind those two visible changes sits something less glamorous and more important: an audit of the whole codebase. It turned up three separate ways you could lose bookmarks, a folder of your private data that was readable by anyone who could reach the app, and outage alerts that never left the building for an entire category of users. All of that is fixed here, and none of […]
Every release of nextDash up to now has carried a date instead of a version number: v2026.09.09, v2026.09.09.1, v2026.09.09.2, and so on, a new tag almost every day through a long stretch of active development. v1.0.0, released today, breaks that pattern on purpose. It’s the first release under semantic versioning, and it’s a deliberate milestone rather than an incremental one: after a long run of bug fixing and consolidation, the app finally feels finished and stable rather than in flux. From here, 1.x.0 releases carry new features and 1.0.x releases carry fixes — a distinction the date-based scheme never made. The comparison logic for the new numbering actually shipped a few point releases earlier, under v2026.09.09.3, so v1.0.0 is really the moment the switch was made official. What’s inside is almost entirely correctness work, and it follows one recurring shape: an operation that reported success for something it hadn’t actually […]
