Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tags, to v or not to v? #59

Open
geemus opened this issue May 22, 2024 · 1 comment
Open

tags, to v or not to v? #59

geemus opened this issue May 22, 2024 · 1 comment

Comments

@geemus
Copy link

geemus commented May 22, 2024

Hey, just wanted to call this out since it has caught me out a couple of times now.

Most of the vX.Y releases actually have tags that just look like X.Y (ie they don't have the leading v like their matching release does). There are a few exceptions (v1 and v1.4 for instance), but that led to me just bumping from v1.4 (which does exist) to v1.5 (which doesn't exist, although 1.5 does).

It would be helpful if this were more consistent. I think superfly might be the only action that I interact with regularly that doesn't use v prefixes consistently, which I suspect also makes it all the more likely that I would make this kind of mistake.

Any way that this could be resolved to be more consistent and/or that future releases have both kinds of tags if you want to go that route?

Thanks.

@thewilkybarkid
Copy link

This caught me out too a while back: #24 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants