Versioning scheme changed backwards

[guillemj]

Hi!

It looks like the versioning scheme changed from X.Y.Z to vM.N.O, but the versioning got reset backwards from 1.10.1 to 1.0.0. This has the consequence that the package is currently stuck in most distributions on the old 1.10.1 release, as the automatic distribution upstream version checks (or human ones) are not detecting the new version. And for the ones that might have noticed, that would imply adding an epoch, which has its own set of global versioning drawbacks (as the epochs invalidate all current versioned dependencies). See https://repology.org/project/go:github-smartystreets-assertions/versions for current distribution status.

Would it be possible to release a new version and bump it to say v1.11.0? That'd be highly appreciated!

(There's a build failure bug in Debian, which I assume is fixed by latest upstream code, but we cannot update it right away due to this. :/ )

[drew-parsons]

I could suggest the new next version be set to v1.12.2 to provide a visual simulation of continuity from the preceding v1.2.1

[openarun]

Any update on this please? :)

[joliver]

Resolved with new v1.13.0 tag.