Versioning is one of those things that seems trivial until it isn't. In a recent update to vibe-coding-universal, we tackled a small but persistent annoyance in our comparison tables: the "Old Version" label. After the latest release cycle, we fixed it to display v1.0 specifically. No more ambiguity for users comparing features across releases.
The Problem: Ambiguous Labels in Version Comparisons
Vibe-coding-universal maintains a set of comparison tables that let developers quickly diff features between releases. These tables are used in documentation, inline UI tooltips, and even generate previews in the CLI. Originally, the tables simply labeled any prior version as "Old Version" — a placeholder we carried over from early prototyping.
While functional, this label caused confusion. When a user compared v1.0 against v0.9, both entries showed "Old Version" and "v1.0" interchangeably, depending on which version was selected. Worse, if someone referred to the table in a ticket or a commit message, they had to decode which "Old Version" corresponded to which actual release. The fix was straightforward: map version labels explicitly in the comparison logic.
The Fix: Explicit Version Mapping in Table Rendering
