Inconsistent tags naming

[BlueskyFR]

From the README:

Sticking with a tagged release might offer better trade-offs going forward.

Although tag names seem to be inconsistent: 1.5.0 vs v1.5.1 for the latest one.

Also, there is no easy way to auto update from 1.5.0 to 1.5.1 using this mechanism.

Isn't there a true versioning method you can use for the flake instead of that?

Thanks!

[gytis-ivaskevicius]

yeah, i was doing them manually and did not pay too much attention. I should probably fix that

Isn't there a true versioning method you can use for the flake instead of that?

I am not sure what you mean

[BlueskyFR]

I recommend rewriting all tags as major.minor.patch for ease of use.

Although the current method does not allow seamless upgrades for end users, thus requiring a manual check every now and then... This may be a Flake limitation but it would be weird!

Isn't there a proper way to allow upgrading automatically to the latest version?

My very limited knowlegde of flakes tells me that either master should always be stable, or a stable branch should exist, in which every new stable release would be merged into.

[gytis-ivaskevicius]

oh, I see what you mean. It is okay to use master, it generally is the latest release candidate and this project is not actively developed since it is "complete" so it's not like you will get many updates anyway

[BlueskyFR]

Okay, thanks for the answer!