You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It makes sense to keep GTO tags in a single format (not supporting it with v and without) both for simplicity of what you can expect to see and different corner cases that may arise, so I wonder, is it just something that doesn't look right (since it's not vanilla semver) or it block some scenarios for you?
Thanks for that link, I'll give it a careful read. In the meantime, I can explain where I'm coming from.
I'm not aware of any strict incompatibility with another tool. My request is motivated purely by trying to put together a nice UX that's as consistent as possible - and our Python packages are indexed with regular semver. So it's less that it doesn't look right (an aesthetic concern) and more that I'll have to explain to other users, who don't know gto, that there is a special convention they have to follow for exactly one step in a multi-step process. This creates friction and opportunities for user errors. I'd rather get ahead of the support tickets and use consistent versioning across all steps.
aguschin
added
design
Design questions, that affects the product significantly
and removed
epic
Epic level issue (>2 weeks)
labels
Aug 30, 2023
Hi,
Would it be possible to make the "v" in "v1.2.3" optional? It's not strict semver. https://semver.org/#is-v123-a-semantic-version
Thanks! :)
The text was updated successfully, but these errors were encountered: