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

suggesstion: use v1.1.1 format when release version #3

Open
thinkerou opened this issue Aug 16, 2019 · 5 comments
Open

suggesstion: use v1.1.1 format when release version #3

thinkerou opened this issue Aug 16, 2019 · 5 comments

Comments

@thinkerou
Copy link

No description provided.

@thaJeztah
Copy link

thaJeztah commented Nov 28, 2019 •
edited
Loading

ping @taowen is it possible to add a new v1.0.3 tag to assist projects that switched to go mod (which requires the v prefix)?

edit: changed v1.1.1 -> v1.0.3

@thaJeztah thaJeztah mentioned this issue Nov 28, 2019
Merged
@thaJeztah
Copy link

ping @taowen PTAL 🤗

@mrhwick
Copy link

mrhwick commented Feb 27, 2020 •
edited
Loading

Also experiencing build errors from gofmt output on a project which depends on this library (via other dependencies, it seems) after switching that project to use go modules.

@thaJeztah
Copy link

@taowen ptal

@Hellseher
Copy link

Ping to add v and go.mod.

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
4 participants
@mrhwick @thaJeztah @thinkerou @Hellseher