Proposal for an extended Semantic Versioning called Epoch SemVer to provide more granular versioning information to users.

Antfu's blog is a hub for Vue.js enthusiasts, featuring tutorials, project showcases, and insights into front-end development with a focus on Vue.js. Developers can explore advanced Vue.js techniques, tooling, and ecosystem integrations, gaining inspiration and practical knowledge to build modern web applications. With Antfu's expertise and creativity, the blog offers resources for Vue.js developers looking to level up their skills.

Anthony Fu

Epoch Semantic Versioning introduces a more granular way to communicate changes in software versions. Instead of traditional semantic versioning, which uses major, minor, and patch versions, it adds an epoch number to signify significant changes. This approach aims to make it easier for users to understand the scale of changes and to adopt updates progressively.

Epoch Semantic Versioning

<blockquote>
For example, UnoCSS would transition from v0.65.3 to v65.3.0 (in the case EPOCH is 0). Following SemVer, a patch release would become v65.3.1, and a feature release would be v65.4.0. If we introduced some minor incompatible changes affecting an edge case, we could bump it to v66.0.0 to alert users of potential impacts. In the event of a significant overhaul to the core, we could jump directly to v100.0.0 to signal a new era and make a big announcement. I’d suggest assigning a code name to each non-zero EPOCH to make it more memorable and easier to refer to. This approach provides maintainers with more flexibility to communicate the scale of changes to users effectively.
</blockquote>
So it’s like primary.major.minor.patch versioning, except it awkwardly uses base 100.
<a href="https://xkcd.com/927/" target="_blank" rel="noopener nofollow">https://xkcd.com/927/</a>