Skip to content

tags, to v or not to v? #59

@geemus

Description

@geemus

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions