vibe-coding-universal is a tool for generating universal code schemas and comparative documentation. One of its core features is the comparison table, which provides a side-by-side view of project versions across features, APIs, or dependencies. Prior to v1.0, these tables displayed a static version label that didn’t update when the project version changed. This fix ensures that all comparison tables now show the correct version label, defaulting to v1.0 for this release, and laying the groundwork for dynamic versioning.
The Problem
The bug was cosmetic but disruptive. In early builds, the version label in comparison tables was hardcoded during template initialization. For example, if you generated a table at v0.9 and later upgraded to v1.0, the output still referenced v0.9. This misled developers viewing reports or documentation, as the tables no longer matched the actual codebase or package metadata. The issue fragmented version histories, especially in CI/CD pipelines where automated comparisons were used for changelogs.
The root cause was a static string in the comparison module’s template engine. The version field did not refresh when the project version was bumped, forcing manual correction or reliance on external versioning tools.
The Fix
Top comments (0)