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

Newer release #82

Open
akkumar opened this issue Jun 28, 2018 · 2 comments
Open

Newer release #82

akkumar opened this issue Jun 28, 2018 · 2 comments

Comments

@akkumar
Copy link

akkumar commented Jun 28, 2018

Since the latest tag / github release - the signatures of NewV1 / V2/ V4 has changed to return an error.

Can we have a github release so it is easier to integrate in dep that way ?

@monkeydioude
Copy link

#80

@vladbarosan
Copy link

@satori can we have a new release with the fixes since the least release ? In general its a good practice to keep master in sync with the latest semantic version

dmitshur added a commit to shurcooL/home that referenced this issue Dec 22, 2018
It seems to be more well maintained and reliable at this time.

google/uuid works out of box with Go modules, because the most recently
tagged version is compatible with master (at this time, they're equal).
On the other hand, using satori/go.uuid requires reverting back to an
older API because its latest tag is more significantly behind master.
See satori/go.uuid#90, satori/go.uuid#82, satori/go.uuid#76.
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

3 participants