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

Repository tagging #42

Open
ScriptTiger opened this issue Nov 21, 2024 · 0 comments
Open

Repository tagging #42

ScriptTiger opened this issue Nov 21, 2024 · 0 comments

Comments

@ScriptTiger
Copy link
Contributor

Is there any public roadmap for tags, such as any particular milestones to be achieved? The last tag was v1.1.0, published on May 22, 2022. And then v1.0.0 before that, published on Apr 5, 2019.

When Go imports a package, unless you specify a specific commit by hash, by default it will just fetch the latest tag, or the latest commit if no tags are present. So, unless people are specifically importing a newer commit by hash, most people who are just using the default built-in Go functionality are still getting v1.1.0 from over 2 years ago.

I know the tag is really only a convenience thing, but there have been a couple significant commits since v1.1.0. So, I was just curious if there was a system to the tagging, or when we'd be due a new tag?

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

1 participant