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

Tag a 1.0.0 release #4

Closed
kyleconroy opened this Issue Aug 28, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@kyleconroy
Copy link

kyleconroy commented Aug 28, 2017

dep, the official experiment in Golang packaging, released it's first stable version last month. dep expects projects to have tagged releases on Github. Could you tag a 1.0.0 release for this repository? Thanks

@dmitshur

This comment has been minimized.

Copy link
Member

dmitshur commented Aug 28, 2017

Sure, I can do that.

I'd like to understand this better, can you tell me more about what are the ways your user experience with dep is worse when this package does not have any releases? How would it be improved once I add a v1.0.0 tag?

@kyleconroy

This comment has been minimized.

Copy link

kyleconroy commented Aug 29, 2017

Sure, here's a concrete example. My Gopkg.lock file currently looks like this:

[[projects]]
  name = "github.com/russross/blackfriday"
  packages = ["."]
  revision = "cadec560ec52d93835bf2f15bd794700d3a2473b"
  version = "v2.0.0"

[[projects]]
  branch = "master"
  name = "github.com/shurcooL/sanitized_anchor_name"
  packages = ["."]
  revision = "541ff5ee47f1dddf6a5281af78307d921524bcb5"

For sanitized_anchor_name, it points to your master branch. In the future, if you ever decide to make a breaking change, updating my dependencies will also cause my code to break. If you instead tag a v1.0.0 tag, I can be sure that I won't accidentally take in new changes.

@SamWhited SamWhited referenced this issue Nov 26, 2018

Merged

Add go.mod file #6

@dmitshur

This comment has been minimized.

Copy link
Member

dmitshur commented Dec 26, 2018

@dmitshur dmitshur closed this Dec 26, 2018

@kyleconroy

This comment has been minimized.

Copy link

kyleconroy commented Dec 28, 2018

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment