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

add mod file #30

Merged
merged 1 commit into from Mar 21, 2019
Merged

add mod file #30

merged 1 commit into from Mar 21, 2019

Conversation

urandom2
Copy link
Contributor

  • go modules will be enabled in 1.13.
  • after merge it would be nice if you would tag this repo: e.g. v1.0.0
    • this will allow consumers something more consistent and readable than v0.0.0-20181229203832-0af3f3b09a0a.

@urandom2 urandom2 mentioned this pull request Mar 21, 2019
1 task
go.mod Show resolved Hide resolved
@gconnell
Copy link
Collaborator

Tagged current release v1.0.0, since it's been nicely stable for a while.

- [go modules](https://github.com/golang/go/wiki/Modules) will be enabled in 1.13.
- after merge it would be nice if you would tag this repo: e.g. `v1.0.0`
  - this will allow consumers something more consistent and readable than `v0.0.0-20181229203832-0af3f3b09a0a`.
@gconnell
Copy link
Collaborator

Thanks!

@gconnell gconnell merged commit bfb3895 into google:master Mar 21, 2019
@urandom2 urandom2 deleted the upstream branch March 21, 2019 16:54
@urandom2
Copy link
Contributor Author

urandom2 commented Mar 21, 2019

since go modules only consume from release tags, can you tag v1.0.1 off master?

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

Successfully merging this pull request may close these issues.

None yet

3 participants