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.

Sign up for GitHub

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

Jump to bottom

Please consider tagging this repo #3

Closed
SamWhited opened this issue Jun 18, 2019 · 1 comment
Closed

Please consider tagging this repo #3

SamWhited opened this issue Jun 18, 2019 · 1 comment

Comments

@SamWhited
Copy link

Hello,

I'm attempting to clean up a go.mod file to make it easier to discover what versions changed. One of the dependencies is this repo, which appears to have no semver compatible tags. Please consider tagging this repo (eg. v0.0.1) so that it is easier to see when it's updated in go.mod files without having to remember dates and hashes.

Thank you for your consideration, and for your work on this module!
@rivo
Copy link
Owner

rivo commented Jul 6, 2019

I did that here now because this version is unlikely to get frequent changes. Note that this is different from the situation over at tview so I'm not planning to re-open that discussion over there for now.

@rivo rivo closed this as completed Jul 6, 2019
shogo82148 added a commit to shogo82148/uniseg-forked that referenced this issue Jul 20, 2023
@shogo82148
Merge pull request rivo#3 from shogo82148/fix-staticcheck-warnings
ee8814c 
Fix staticcheck warnings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rivo @SamWhited